Secure execution of an exchange item acquisition request

ABSTRACT

A method for execution by one or more servers of an exchange item marketplace network includes receiving, from a computing device, an acquisition request regarding an exchange item of a plurality of exchange items of the exchange item marketplace network. The method further includes obtaining user information associated with the computing device and device information associated with the computing device. The method further includes selecting a fraud determination approach of a plurality of fraud determination approaches based on the user information and the device information, where the selected fraud determination approach includes a traversing nodes of a fraud decision tree. The method further includes performing a decision tree analysis function on the fraud decision tree to produce a predicted fraud level for the acquisition request. The method further includes determining whether the predicted fraud level compares favorably to a fraud threshold, and when yes, facilitating execution of the acquisition request.

CROSS REFERENCE TO RELATED PATENTS

The present U.S. Utility Patent Application claims priority pursuant to 35 U.S.C. § 120 as a continuation of U.S. patent application Ser. No. 17/093,149, entitled “SELLER VERIFICATION OF A REQUEST TO SELL AN EXCHANGE ITEM IN AN EXCHANGE ITEM MARKETPLACE NETWORK”, filed Nov. 9, 2020, pending, which is a continuation of U.S. patent application Ser. No. 14/865,293, entitled “METHOD AND APPARATUS FOR A DIGITAL EXCHANGE ITEM MARKETPLACE NETWORK INCLUDING BUYER, SELLER, AND DEVICE VERIFICATION”, filed Sep. 25, 2015, issued as U.S. Pat. No. 10,832,298 on Nov. 10, 2020, which claims priority pursuant to 35 U.S.C. § 119(e) to U.S. Provisional Application No. 62/222,035, entitled “METHOD AND APPARATUS FOR AN EXCHANGE ITEM MARKETPLACE NETWORK,” filed Sep. 22, 2015, expired, all of which are hereby incorporated herein by reference in their entirety and made part of the present U.S. Utility Patent Application for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

NOT APPLICABLE

INCORPORATION-BY-REFERENCE OF MATERIAL SUBMITTED ON A COMPACT DISC

NOT APPLICABLE

BACKGROUND OF THE INVENTION Technical Field of the Invention

This invention relates generally to computer networks and more particularly to an exchange item marketplace network.

DESCRIPTION OF RELATED ART

The use of credit cards, debit cards, and gift cards to pay for goods and services is well known. It is further known to use services such as PayPal™ or Apple Pay™ to expand the use of credit cards and debit cards through computing devices (e.g., computers, tablets, cell phones, etc.). The use of these services is aided by the standardized numbering system and format used by credit card issuers and debit card issuers.

For a credit card and debit card transaction, the credit or debit cardholder presents the credit or debit card to a merchant (e.g., on line or brick & mortar) to pay for a purchase. The merchant uses point of sale (POS) equipment to capture the information of the credit or debit card and to enter the amount of the purchase. This information is sent to an acquirer (e.g., the financial institution of the merchant). The acquirer sends the transaction information via a secure network of a credit card company to the cardholder's issuer (e.g., a financial institution that issued the credit or debit card to the cardholder).

The issuer approves or declines the transaction and sends the response back to the acquirer via the secure network of the credit card company. The acquirer sends the response (e.g., approved or declined) to the merchant to complete the transaction. Money, however, is not exchanged at the time of purchase, but is done during clearing and settlement.

Clearing and settlement begins when the merchant deposits the transaction receipt with the acquirer. The acquirer credits the merchant's account and sends the transaction receipt to the issuer via the secure network. The issuer posts the transaction to the cardholder's account. The cardholder pays the issuer in response to receiving a monthly statement.

The issuance and use of a gift card is significantly different than that of a credit card. FIG. 1 illustrates a diagram regarding the issuance and use of a gift card. A branded company (e.g., a retailer, a chain store, a restaurant, etc.) issues a request to create gift cards to a processor service. The processor service creates the gift cards, which may be issued with specific values or issued as blanks; where the value is specified at the time of purchase.

The processor service provides the gift cards to a distributor who is responsible for distributing the gift cards so that a consumer may purchase them. For example, the distributor may provide gift cards to merchants so they may sell the gift cards. At some point, a consumer purchases a gift card (e.g., a sporting goods company gift card for $50.00). The payment for the gift card is processed such that the distributor, processing service, and branded company each are paid their respective shares.

If the gift card is used, a merchant (e.g., a franchise owner of the branded company) captures information of the gift card via point of sale (POS) equipment. The information of the gift card is processed to determine if it is a valid gift card and to determine the balance remaining on the gift card. If the card is valid, the use of the gift card is authorized up to the balance remaining on the gift card. Once the use is complete, the balance is updated, processing fees are paid, and the branded company is debited.

Another difference between credit cards and gift cards is that gift cards do not have a standardized numbering system or format. As such, gift cards can have one of thousands of different numbering systems and formats, which have to be recognizable by the POS equipment.

Yet another different between credit cards and gift cards is when money is processed. For credit cards, money is not processed until a purchase occurs, while gift cards are purchased and then subsequently used. As such, money is processed at the time of purchase of the gift card and again if the gift card is used.

A still further difference between credit cards and purchased gift cards is that, if a credit card goes unused, no money is spent. In contrast, if a purchased gift card goes unused, money has been spent to acquire the card, but no goods or services are acquired. It is estimated that billions of dollars worth of purchased gift cards go unused annually. While this may be a favorable scenario for the branded company, it is not a favorable scenario for consumers.

Raise Marketplace Inc. introduced a system that enables gift cardholders to sell their unused or unwanted gift cards. This system allows a gift card seller to post a gift card for sale in a virtual gift card marketplace. Buyers can access the virtual gift card marketplace and purchase gift cards that are offered for sale. When a gift card is purchased, the system processes the purchase to debit the buyer, credit the seller, and provide the gift card to the buyer.

The system may provide the physical gift card to the buyer, which requires obtaining the physical gift card from the seller and delivering it to the buyer. Alternatively, the system provides the information of the gift card to the user in a voucher format (e.g., a document that the buyer can print off that includes the relevant information of the gift card).

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING(S)

FIG. 1 is a schematic block diagram of a prior art gift card issuance and use system;

FIG. 2 is a schematic block diagram of an embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 3 is a schematic block diagram of an embodiment of user device of exchange item marketplace network in accordance with the present invention;

FIG. 4 is a schematic block diagram of an embodiment of a marketplace server of exchange item marketplace network in accordance with the present invention; FIG. 5 is a schematic block diagram of an example of operation of an exchange item marketplace network in accordance with the present invention;

FIG. 6A is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 6B is a schematic block diagram of an embodiment of seller portion of an exchange item marketplace network in accordance with the present invention;

FIG. 6C is a schematic block diagram of an embodiment of buyer portion of an exchange item marketplace network in accordance with the present invention;

FIG. 6D is a flowchart illustrating an example of exchanging exchange items within an exchange item marketplace network in accordance with the present invention;

FIG. 7 is a diagram of an embodiment of individual seller verification in an exchange item marketplace network in accordance with the present invention;

FIG. 8 is a logic diagram of an embodiment of a method of individual seller verification in an exchange item marketplace network in accordance with the present invention;

FIG. 9 is a diagram of an embodiment of bulk seller verification in an exchange item marketplace network in accordance with the present invention;

FIG. 10 is a logic diagram of an embodiment of a method of bulk seller verification in an exchange item marketplace network in accordance with the present invention;

FIG. 11 is a logic diagram of an embodiment of a method of verification of an exchange item in an exchange item marketplace network in accordance with the present invention;

FIG. 12 is a logic diagram of an embodiment of a method of adding and deleting an exchange item to an exchange item marketplace network in accordance with the present invention;

FIG. 13 is a logic diagram of an embodiment of a method of buyer verification in an exchange item marketplace network in accordance with the present invention;

FIG. 14 is a logic diagram of an embodiment of a method of exchange item payment in an exchange item marketplace network in accordance with the present invention;

FIG. 15 is a logic diagram of an embodiment of a method of exchange item balance update in an exchange item marketplace network in accordance with the present invention;

FIG. 16 is a schematic block diagram of another embodiment of an exchange item marketplace network in accordance with the present invention;

FIG. 17A is a schematic block diagram of an embodiment of a seller device interfacing with a marketplace server in accordance with the present invention;

FIG. 17B is a logic diagram of an embodiment of a method for a seller device to interface with a marketplace server in accordance with the present invention;

FIG. 18A is a schematic block diagram of another embodiment of a seller device interfacing with a marketplace server in accordance with the present invention;

FIG. 18B is a logic diagram of another embodiment of a method for a seller device to interface with a marketplace server in accordance with the present invention;

FIGS. 19A and 19B are schematic block diagrams of an embodiment of a buyer device interfacing with a marketplace server in accordance with the present invention;

FIG. 19C is a logic diagram of an embodiment of a method for a buyer device to interface with a marketplace server in accordance with the present invention;

FIGS. 20A-20C are schematic block diagrams of an embodiment of a buyer device interfacing with a marketplace server regarding buyer verification in accordance with the present invention;

FIG. 20D is a logic diagram of an embodiment of a method for a buyer device to interface with a marketplace server regarding buyer verification in accordance with the present invention;

FIG. 21A is a schematic block diagram of an embodiment of a buyer device interfacing with a marketplace server regarding buyer purchase in accordance with the present invention; and

FIG. 21B is a logic diagram of an embodiment of a method for a seller device to interface with a marketplace server regarding buyer purchase in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 2 is a schematic block diagram of an embodiment of an exchange item marketplace network 10 that includes user devices 12 of individual sellers, user devices 14 of bulk sellers, user devices 16 of individual buyers, one or more marketplace servers 18 (an example embodiment is shown in FIG. 4), one or more databases 20, one or more networks 24, one or more brand servers 26, one or more processor servers 28, one or more distributor servers 30, point of sale (POS) equipment 32, and one or more retailer servers 34. The one or more marketplace servers 18 process, and the one or more databases 20 store a virtual marketplace of exchange items 22.

Each of the user devices 12, 14, and 16 is a computing device that includes a computing core. In general, a computing device is any electronic device that can communicate data, process data, and/or store data. A further generality of a computing device is that it includes a central processing unit (CPU), a memory system, user input/output interfaces, peripheral device interfaces, and an interconnecting bus structure.

As specific examples, each of the user devices 12 — 16 may be a portable computing device and/or a fixed computing device. A portable computing device may be a social networking device, a gaming device, a cell phone, a smart phone, a personal digital assistant, a digital music player, a digital video player, a laptop computer, a handheld computer, a tablet, a video game controller, and/or any other portable device that includes a computing core. A fixed computing device may be a personal computer (PC), a computer server, a cable set-top box, a satellite receiver, a television set, a printer, a fax machine, home entertainment equipment, a video game console, and/or any type of home or office computing equipment that includes a computing core. An embodiment of a computing device 12-16 is further described below with reference to FIG. 3.

The exchange item marketplace network 10 supports the selling and purchasing of exchange items. An exchange item is a closed loop financial instrument and/or other digital goods. For example, a closed loop financial instrument is a gift card, a voucher, a store credit, and/or other brand company (or merchant) sponsored form of credit for a specific use (e.g., in a specific store, in a specific chain of stores, for a particular type of goods, etc.). A closed loop financial instrument is distinguished from an open loop financial instrument, such as a credit card.

A digital good is digital item that can legally be sold or resold by an individual. For example, the digital item may be an original digital book, an original digital photograph, an original video clip, a purchased video game, a purchased software application, a purchase video, a purchased music file, a purchased digital book, a purchased audio book, etc.

In support of selling an exchange item, the marketplace server 18 communicates with a user device of a seller (e.g., individual or bulk) to verify the user device (and the seller) and to ascertain information regarding the exchange item being offered for sale. For example, the marketplace server 18 verifies user information (e.g., the seller's name, account, personal identification number (PIN), a user identification number (ID), payment account information (e.g., a credit card number, checking or savings account information), seller's mailing address, etc.) and device information (e.g., an IP address, device serial number, a marketplace application ID, etc.) of the seller's computing device. Verification of the seller and corresponding computing device is discussed in greater detail with reference to one or more of FIGS. 6A-6D, 7-10, 18A, and 18B.

Upon receiving the information regarding the exchange item, which includes a brand name (e.g., a coffee franchise, a sporting good franchise, an electronics store, etc.), a serial number, a selling price, a remaining balance, restrictions of use, a bar code, and/or other pertinent information, the marketplace server 18 verifies it. When the seller and the information regarding the exchange item are verified, the marketplace server 18 posts it in the virtual marketplace of exchange items 22, which is stored in database 20.

The marketplace server 18 posts the exchange item in the virtual marketplace 22 by creating a digital representation of the exchange item. To do this, the server creates a digital image of the exchange item, determines the brand of the exchange item, and the information regarding the exchange item (e.g., a brief description, brand, selling price, balance, serial number, restrictions (if any), expiration date (if any), and/or any other pertinent information). In accordance with an organization protocol of the virtual marketplace, the digital representation of the exchange item is added. For instance, the organization protocol groups exchange items by types (e.g., restaurants, sporting goods, coffee shops, automotive goods, etc.), by brands (e.g., a sporting goods chain, a coffee shop chain, etc.), by sales price, by balance of the exchange item, by a savings value (e.g., a difference between the balance and the sales price), by expiration date, by date offered for sale, by special promotions, by seller, by restrictions, by a brief description (e.g., title of a video for resale), and/or any other organization scheme that lends itself to searching for particular items. As such, for a particular exchange item offered for sale, its digital representation is added to the database 20 and will be displayed within a grouping per the organization protocol when a potential buyer or other user of the system 10 selects the grouping. In one example, if the exchange item is a gift card, a digital image of the gift card is displayed along with at least some of the related information (e.g., sales price, balance, etc.). If the gift card includes a logo of the branded company offering the gift card, the logo is often displayed in accordance with requirements of the branded company.

A potential buyer of an exchange item offered for sale access the system 10 using its user device 16. For example, the user device 16 logs into the system 10. If the user device 16 is associated with a buyer that does not have an account with the system 10, the buyer creates one through the user device 16 with the system. For buyers with an account, the marketplace server 18 verifies the buyer user device 16 before allowing it access to the virtual marketplace 22. The buyer verification process is discussed in greater detail with reference to one or more of FIGS. 5, 6A-6D, 13, and 20A-20D.

Once the buyer is verified, the buyer computing device 16 is allowed access the virtual marketplace 22. The buyer computing device 16 uses searching criteria that are in accordance with the organization protocol to search the virtual marketplace 22 for exchange items of interest.

The marketplace server 18 provides video-graphics data to the buyer computing device 16 in accordance with the searching. When the buyer computing device 16 finds exchange items of interest, it displays the video-graphics of the corresponding exchange items (e.g., a grouping of gift cards).

The buyer computing device 16 receives an input corresponding to a selection of one of the exchange items of interest for purchase. The buyer computing device 16 sends the selected exchange item to the marketplace server 18 for processing.

The marketplace server 18 processes the selected exchange item via a multiple step process. One step includes verifying that the buyer is authorized to purchase the exchange item (e.g., has the financial resources, is not limited by buying restrictions (e.g., dollar amount, quantity, type, etc.), is a legitimate buyer, etc.). Another step includes verifying integrity of the information of the selected exchange item (e.g., balance remaining is accurate, the offer to sell the exchange item has not been withdrawn, the exchange item is not currently being processed for sale to another buyer, the exchange item is not expired, the exchange item has not been voided by the branded company, etc.).

When the buyer is authorized and the information regarding the selected exchange item has been verified, another step includes removing the exchange item from the virtual marketplace 22. Another step includes processing payment for the selected exchange item. The multiple step buying process is further described with reference to one or more of FIGS. 5, 6A-6D, 11-14, and 20A-20D.

FIG. 3 is a schematic block diagram of an embodiment of computing device 12-16 of exchange item marketplace network 10. The computing device 12-16 includes a computing core 52, one or more input devices 54 (e.g., keypad, keyboard, touchscreen, voice to text, etc.), one or more audio output devices 56 (e.g., speaker(s), headphone jack, etc.), one or more visual output devices 58 (e.g., video graphics display, touchscreen, etc.), one or more universal serial bus (USB) devices, one or more networking devices (e.g., a wireless local area network (WLAN) device 84, a wired LAN device 86, a wireless wide area network (WWAN) device 88 (e.g., a cellular telephone transceiver, a wireless data network transceiver, etc.), and/or a wired WAN device 90), one or more memory devices (e.g., a flash memory device 92, one or more hard drives 94, one or more solid state (SS) memory devices 96, and/or cloud memory 98), and one or more peripheral devices.

The computing core 52 includes a video graphics processing unit 60, one or more processing modules 62, a memory controller 64, main memory 66 (e.g., RAM), one or more input/output (I/O) device interface module 68, an input/output (I/O) interface 70, an input/output (I/O) controller 72, a peripheral interface 74, one or more USB interface modules 76, one or more network interface modules 78, one or more memory interface modules 80, and/or one or more peripheral device interface modules 82. Each of the interface modules 68, 76, 78, 80, and 82 includes a combination of hardware (e.g., connectors, wiring, etc.) and operational instructions stored on memory (e.g., driver software) that is executed by the processing module 62 and/or a processing circuit within the interface module. Each of the interface modules couples to one or more components of the computing device 12-16. For example, one of the IO device interface modules 68 couples to an audio output device 56. As another example, one of the memory interface modules 80 couples to flash memory 92 and another one of the memory interface modules 80 couples to cloud memory 98 (e.g., an on-line storage system and/or on-line backup system). FIG. 4 is a schematic block diagram of an embodiment of a marketplace server 18 of exchange item marketplace network 10. The server 18 includes a computing core 122, one or more input devices 54 (e.g., keypad, keyboard, touchscreen, voice to text, etc.), one or more audio output devices 56 (e.g., speaker(s), headphone jack, etc.), one or more visual output devices 58 (e.g., video graphics display, touchscreen, etc.), one or more networking devices (e.g., a wireless local area network (WLAN) device 84, a wired LAN device 86, a wireless wide area network (WWAN) device 88 (e.g., a cellular telephone transceiver, a wireless data network transceiver, etc.), and/or a wired WAN device 90), one or more memory devices (e.g., a flash memory device 92, one or more hard drives 94, one or more solid state (SS) memory devices 96, and/or cloud memory 98), and one or more peripheral devices. Note that the server 18 may include more or less devices than shown in this example embodiment of a server. The computing core 122 includes a video graphics processing unit 60, a plurality of processing modules 62, a memory controller 64, a plurality of main memories 66 (e.g., RAM), one or more input/output (I/O) device interface module 68, an input/output (I/O) interface 70, an input/output (I/O) controller 72, a peripheral interface 74, one or more network interface modules 78, and/or one or more memory interface module 80.

FIG. 5 is a schematic block diagram of an example of operation of an exchange item marketplace network 10. In this example, an exchange item (EI) issuer 130 issues a plurality of exchange items (e.g., closed loop financial instruments and/or other digital goods), which are distributed to consumers by an EI distributor 132. At some point in time, a consumer owns one of the exchange items (e.g., purchases the exchange item, is given the exchange item as a gift, is given the exchange item as compensation, etc.). At some later point in time, the owner of the exchange item decides to sell it.

To sell the exchange item, the owner of the EI evokes an EI marketplace (MP) interface module 142 on its computing device 12 or 14. The EI MP interface module 142 includes a browser application, a mobile device application, and/or any type of application that enables access to the virtual marketplace of exchange items 22. The computing core 52 of the user device executes one or more of these applications. For instance, each of the applications includes operational instructions that are stored in memory (e.g., main memory, flash memory, SS memory, HD memory, and/or cloud memory) and executed by the processing module 62 of the computing core 52. Alternatively, the EI MP interface module 142 includes a processing circuit and memory, wherein the memory stores and the processing circuit executes the operational instructions of the application. As yet another alternative, the processing circuit of the EI interface module 142 and the processing module 62 of the computing core 52 co-process the operational instructions of one or more of the applications.

With the EI MP interface module 142 operational on the computing device 12, the computing device 12 provides information regarding the EI for sale to the server 18 of the network 10. The information includes a type of EI (e.g., a gift card, a voucher, a credit, a digital good, etc.), brand information, if any, (e.g., a chain store, a restaurant, etc.), a balance remaining on or value of the exchange item, a sales price, a serial number and/or other identifying data regarding the exchange item.

The server 18 digitizes the exchange item to create a digital exchange item 152, which is added to the virtual marketplace of exchange items 22. For example, if the exchange item is a gift card, the digital exchange item 152 is a digital representation of the gift card (e.g., a rendered digital picture of the gift card, including any relevant logos). As another example, if the exchange item is a digital good (e.g., a video game), the digital exchange item 152 is a digital representation of packaging of the digital good. Note that the server 18 may be interacting with hundreds to hundreds of thousands of seller computing device 12-14 to post exchange items for sale in the virtual marketplace of exchange items 22.

For an exchange item 152 in the virtual marketplace of exchange items 22, its digital representation is displayed along with its relevant information (e.g., sales price, a discount percentage, restrictions (if any), etc.). The exchange item 152 is typically grouped and displayed with other like exchange items. For example, if the exchange item is a gift card for a particular coffee shop, it is grouped with other gift cards from the same coffee shop. The grouping of like exchange items may be further refined by sub-grouping based on one or more of sales price, time on the marketplace, discount amount, remaining balance, etc.

A buyer desiring to purchase an exchange item offered for sale 160 in the marketplace of exchange items 22 utilizes its computing device 16 and its EI MP interface module 142 to access the marketplace 22. While accessing the marketplace 22, the buyer, via the EI MP interface module 142 and the computing device 16 selects one of the exchange items to purchase, which is shaded gray.

The server 18 processes the selection of the exchange item by verifying the buyer, the buyer's computing device, the buyer's purchasing abilities, and/or the information regarding the selected exchange item. When verified, the server removes the selected exchange item from the marketplace 22 and places it in the buyer's digital wallet 148. To do this, the server processes the buyer's wallet information 168 (e.g., the buyer's ID, buyer account ID, buyer use restrictions (if any), etc.) and the information 166 of the selected exchange item. For example, the buyer's digital wallet includes a digital representation of the recently purchased exchange item and the corresponding information. The recently purchased exchange item is displayed in a categorical manner (e.g., date of purchase, type of exchange item, value or remaining balance of exchange item, etc.).

In addition, the server processes the financial transaction for the purchase of the selected exchange item. For example, the server 18 communicates with the financial server of the buyer to receive the funds for the purchase. The server then dispenses the funds to the seller, less processing and/or commission fees. The funds may be dispensed to seller in a variety of ways. For example, the server 18 transfers the seller's funds to a financial server of the seller (e.g., the seller's bank and/or other financial service institution). As another example, the server provides the funds to the seller's digital wallet 146, which is maintained by the server 18. The seller may withdraw the funds, or a portion thereof, from its wallet (e.g., as instructed via the seller's computing device, the server 18 transfers the selected amount of the funds to the seller's financial service's server). As another example, the seller acts as a buyer to buy an exchange item from the marketplace 22 and the funds in the wallet are used to pay for the purchased exchange item.

When the buyer utilizes the exchange item, certain transaction information associated with the utilizing of the exchange item may be communicated as EI use information 172 to a merchant 140. The EI use information 172 includes one or more of a brand identifier, a balance, an amount utilized for a utilization transaction, and a timestamp.

FIG. 6A is a schematic block diagram of another embodiment of an exchange item (EI) marketplace (MP) network that includes the seller's computing device 12, the buyer's computing device 16, a seller's financial server 190, a service provider's financial server 192, a buyer's financial server 194, the marketplace (MP) server(s) 18, and the database 20, which includes the virtual marketplace of exchange items 22. Each of the seller's computing device 12 and buyer's computing device 16 includes the (EI) marketplace interface 142, which includes a web browser 196 and a mobile application 198.

The MP server 18 performs function blocks that includes a seller verification 200, a deny 202, an exchange item verification 204, an add exchange item to marketplace 206, a buyer verification 208, a deny 210, an exchange item purchase verification 212, an exchange item payment processing 214, a remove exchange item from marketplace 216, an add exchange item to buyer's wallet 218, an exchange item use 220, and an exchange item balance update 222.

As an example of operation, the mobile application 198 of the seller's computing device 12 sends a request to sell an exchange item to the marketplace (MP) server(s) 18. The server 18 performs the seller verification 200 functional block to determine whether the seller and/or the seller's computing device 12 are a valid seller (e.g., device and/or seller are valid). When invalid, the server(s) 18 performs the deny 202 functional block to communicate a denial of the request to sell the exchange item to the seller's computing device 12.

When the seller is verified, the server performs the exchange item verification 204 functional block to determine whether the exchange item is valid (e.g., is a valid exchange item, perform a balance check with an associated entity, i.e., a retailer, etc.). When invalid, the server(s) perform the deny 202 functional block. When the exchange item is valid, the server(s) 18 perform the add exchange item to marketplace 206 functional block to add a digital representation of the exchange item to the virtual marketplace of exchange items 22 (e.g., creates a new entry for inventory within the virtual marketplace of exchange items 22).

When a buyer desires to purchase an exchange item, the mobile application 198 of the buyer's computing device 16 sends a request to buy a selected exchange item to the MP server(s) 18. The server(s) 18 perform the buyer verification 208 functional block to determine whether the buyer is valid (e.g., the user and/or buyer computing device are valid). When invalid, the server(s) 18 perform the deny 210 functional block to issue a denial of the purchase request to the buyer's computing device 16.

When the buyer is validated, the server(s) 18 perform the exchange item purchase verification 212 functional block to verify that the buyer, via the buyer's computing device, has sufficient means (e.g., money, credit, valid credit card, valid debit card, etc.) to pay for the selected exchange item. For example, the exchange item purchase verification 212 functional block enables the server 18 to receive buyer information from the buyer's financial server 194 verifying payment and/or verifying an ability to pay. When unable to purchase the selected exchange item, the server 18 performs the deny 210 functional block.

When the buyer is able to purchase the selected exchange item, the server 18 performs the exchange item payment processing 214 functional block to process payment for the selected exchange item. For example, the server 18 collects payment from the buyer's e-wallet, the buyer's computing device 16, or the buyer's financial server 194, issues a payment to the seller's e-wallet, to the seller's computing device, or to the seller's financial server 190, and issues a commission payment to the service provider's financial server 192.

After processing payment or concurrent with the processing of the payment, the server 18 performs the remove exchange item from marketplace 216 functional block to remove the selected exchange item from the virtual marketplace of exchange items 22. For example, the server 18 deletes an entry associated with the selected exchange item from the database 20.

The server 18 performs the add exchange item to the buyer's wallet 218 functional block to facilitate adding the exchange item to a buyer's e-wallet. For example, the server 18 updates a representation of the buyer's wallet within the database 20 to include a digital representation of the purchased exchange item and issues a message to the mobile application 198 to store a local copy of the digital representation within the buyer's computing device 16.

When the buyer desires to purchase something using an exchange item, the mobile application 198 communicates a utilization message to the server 18. The server 18 evokes the exchange item use 220 functional block to receive the utilization message and to facilitate communication with other servers for verification and transaction execution. For example, the server 18 forwards the utilization message to a retailer server associated with the exchange item to initiate execution of the transaction. Having successfully used the exchange item, the server 18, via the exchange item balance update 222 functional block, updates the buyer's wallet to indicate that the exchange item has been utilized and to update the balance remaining on the exchange item, when appropriate.

FIG. 6B is a schematic block diagram of an embodiment of seller portion of an exchange item marketplace network that includes a plurality of seller's computing devices 12, the marketplace (MP) server(s) 18, and the database 20, which stores the virtual marketplace 22. Each of the seller's computing devices 12 include the marketplace interface 142, which includes the web browser 196 and the mobile application 198.

The MP server 18 includes a first module 230 to process receiving of requests to sell exchange items 234 and a second module 232 to process a selected request to sell an exchange item. The second module 232 includes several sub-modules (e.g., more modules). In an embodiment, the second module 232 includes the seller verification 200 functional block, the exchange item verification 204 functional block, and the add exchange item to marketplace 206 functional block.

In an example of operation, the first module 230 receives requests to sell exchange items (EI) 234 from the seller computing devices 12. Each request includes information regarding the exchange item being offered for sale. The information includes one or more of a selling price, branding information, a description of the exchange item (if applicable), a value of the exchange item, restrictions regarding the exchange item, etc.

The first module 230 provides the requests to the second module 232, which processes the requests to sell in a serial manner, in a parallel manner, and/or in a combined serial-parallel manner. For each request to sell, the second module 232 processes the request via the seller verification functional block 200, the exchange item verification functional block 204, and the add exchange item to the marketplace functional block 206.

The server(s) 18 perform the seller verification functional block 200 to verify seller information (e.g., information regarding the seller and/or information regarding the seller computing device). Accordingly, the server 18 verifies the information regarding the seller and/or seller computing device by one or more of verifying user information (e.g., user name, user account number, personal information number (PIN), user identifier, payment account info, etc.) associated with the seller computing device and verifying device information (e.g., Internet protocol (IP) address of the seller user device, authorized seller user device serial number, the seller user device is utilizing an authorized mobile application 198, etc.) of the seller computing device.

When the seller information is favorably verified 238, the server 18 performs the exchange item verification functional block 204 to verify information regarding the exchange item being offered for sale. Accordingly, the server 18 determines validity of one or more of a brand identifier (e.g., and/or an exchange item type indicator) of the exchange item, a value of the exchange item, and a serial number of the exchange item. For example, the server 18 compares the information regarding the exchange item provided by the seller to information and/or rules stored in the database 20. For instance, the server verifies the serial number and/or format of the serial number for the brand identifier. Further, the server 18 verifies the value of the exchange item by issuing a value verification request to an external entity and receiving a verification response thereto.

When the exchange item is verified 240, the server 18, via the exchange item verification 204 functional block, further determines a selling price for the exchange item. For instance the server uses one or more seller software tools as is discussed with reference to FIG. 16.

The server 18 also performs the add exchange item to marketplace functional block 206 to add the exchange item to marketplace of exchange items 22 (e.g., a digital exchange item marketplace). The adding includes creating a digital representation of the exchange item. The digital representation of the exchange item includes one or more of an image of the exchange item when the exchange item is a physical entity, the brand, serial number, the value, the selling price, the discount level, and the identifier of the seller user device. The adding further includes associating the selling price with the digital representation of the exchange item and adding the digital representation with the associated selling price to the digital exchange item marketplace. For example, the add exchange item to marketplace 206 issues exchange item information 242 to the database 20 for storage in the virtual marketplace of exchange items 22. The exchange item information 242 includes one or more of the association of the selling price to the digital representation and the digital representation of the exchange item.

FIG. 6C is a schematic block diagram of an embodiment of buyer portion of an exchange item marketplace network that includes buyer's computing devices 16, the marketplace (MP) server(s) 18, the database 20 that stores the virtual marketplace 22, the buyer's financial server 194, the service provider's financial server 192, and the seller's financial server 190. Each buyer computing device 16 includes the marketplace interface 142, which includes the web browser 196 and the mobile application 198.

The MP server 18 includes a third module 250 to receive requests to buy and a fourth module 252 to process the requests to buy. The fourth module 252 includes the buyer verification 208 functional block, the exchange item purchase verification 212 functional block, the exchange item payment processing 214 functional block, the remove exchange item from marketplace 216 functional block, and the add exchange item to buyer's wallet 218 functional block.

In an example of operation, the third module 250 receives requests to buy 254 from the buyer computing devices. Each request to buy 254 includes one or more of a brand identifier, an exchange item (EI) type indicator, a purchase price, a purchase price range, purchase terms (e.g., payment timing, delivery timing, payment method, etc.), buyer payment account information (e.g., credit or debit card information, Apple Pay™ information, PayPal™ information, etc.), buyer user device information (e.g., buyer name, exchange item marketplace identifier, etc.), security information (e.g., buyer PIN, digital security certificate information, etc.), and other buyer information (e.g., security question responses, etc.). The server(s) 18 process the requests to buy in a serial manner, in a parallel manner and/or in a serial-parallel manner. For example, the server 18 may process the requests to buy based on one or more of a random selection, a first in first out approach, a buyer prioritization approach, a brand based approach, a discount level approach, a serial number based approach, an EI value ranking approach, and a market efficiency optimizing approach.

The fourth module 252 begins processing of a request to buy via the buyer verification 208 functional block to verify buyer information (e.g., buyer information and/or information regarding the computing device). The verifying includes one or more of verifying user information (e.g., buyer name, buyer account information, buyer PIN, buyer user ID, buyer payment account info, etc.) associated with the buyer computing device, verifying device information (e.g., buyer user device IP address, buyer user device serial number, version of buyer's user device mobile application 198, etc.) of the buyer computing device, and executing a verification tree process.

The buyer verification 208 functional block includes a verification tree process that issues a series of questions to the buyer computing device and/or the buyer's financial server 194, receives a series of responses from the buyer computing device, and evaluates the series of responses in an effort to verify the information regarding the buyer computing device. An example of the verification tree process will be discussed in greater detail with reference to one or more of FIGS. 20A-20D.

When the information regarding the buyer computing device is favorably verified, the server 18 performs the exchange item purchase verification 212 functional block to verify payment. The verifying includes verifying information regarding the selected exchange item and verifying buyer payment account information in light of the verified information regarding the selected exchange item.

The verifying the information regarding the selected exchange item includes one or more of accessing the virtual marketplace of exchange items 22 to verify that the selected exchange item is still for sale, verifying that an alternative exchange item is available when the selected exchange item is now unavailable, verifying the balance, verifying the purchase price to a selling price, and verifying that any selling restrictions are met (e.g., transaction timing, payment type, etc.). The verifying buyer payment account information includes one or more of receiving buyer information 260 from the buyer's financial server 194 indicating payment approval, verifying that any buying restrictions have been met, and verifying validity of buyer financial payment information. For example, the exchange item purchase verification 212 indicates favorable payment verification information when verifying that the selected exchange item is still available for sale at the purchase price and that the buyer user device 16 is able to make the payment.

When the payment information is favorably verified, the server 18 performs the exchange item payment processing 214 functional block to process payment for the selected exchange item.

The server 18 processes the payment for the selected exchange item utilizing one or more payment processing steps. As an example of the one or more payment processing steps, the exchange item payment processing 214 functional block determines a transaction processing fee (e.g., a credit card payment fee of 3% of the selling price), determines a commission fee (e.g., a flat rate fee of 15% of the selling price for the marketplace operator, a variable fee based on other factors, may further include the transaction processing fee), debits an account associated with the buyer computing device for the selling price of the selected exchange item (e.g., completing a transaction with the buyer's financial server 194), credits an account associated with the seller computing device for the selling price less the commission fee (e.g., issues payment processing information 266 to the seller's financial server 190), and credits one or more accounts for the transaction processing fee and for the commission fee (e.g., issuing payment processing information 264 for the commission fee to the service provider's financial server 192).

When the payment processing information 264 indicates that the payment has been successful, the server 18 performs the remove exchange item from marketplace 216 functional block to remove the selected exchange item from the digital exchange item marketplace. In addition, the server performs the add exchange item to buyer's wallet 218 functional block to add the selected exchange item to a digital wallet associated with the buyer computing device. For example, when the digital wallet is active, the server provides a digital representation of the selected exchange item and exchange item information to the buyer's computing device for display thereon. For example, the server 18 generates wallet information 272 from the exchange item information and sends the wallet information 272 to the buyer's computing device 16 for storage and display. The wallet information 272 includes the digital representation (e.g., an image of the exchange item when the exchange item represents a physical item) of the selected exchange item and the exchange item information (e.g., EI type, brand, balance, serial number, PIN, etc.).

FIG. 6D is a flowchart illustrating an example of buying and selling exchange items within an exchange item marketplace network. The method includes step 290 where a processing module of a computing device and/or a server receives requests to sell exchange items from seller computing devices. For a request to sell, the method continues at step 292 where the processing module processes the request to sell by verifying information regarding a seller's computing device associated with the request to sell. The verifying includes one or more of verifying user information (e.g., seller name, seller account, seller PIN, seller ID, seller payment account info, etc.) associated with the seller computing device and verifying device information (e.g., seller user device IP address, seller user device serial number, seller user device application information, etc.) of the seller's computing device.

When the information regarding the seller's computing device is favorably verified, the method continues at step 294 where the processing module verifies information regarding an exchange item identified in the request to sell. The verifying includes determining that a brand identifier of the exchange item, a value of the exchange item, and a serial number of the exchange item are valid. When the brand identifier of the exchange item, the value of the exchange item, and the serial number of the exchange item are valid, the method continues at step 296 where the processing module determines a selling price for the exchange item. For example, the processing module utilizing seller software tools to establish a selling price.

When the information regarding the exchange item is favorably verified, the method continues at step 298 where the processing module adds the exchange item to a digital exchange item marketplace. The adding includes one or more of creating a digital representation of the exchange item, associating a selling price with the digital representation of the exchange item, and adding the digital representation with the associated selling price to the digital exchange item marketplace.

The method includes step 300 where the processing module receives requests to buy exchange items from buyer computing devices. For a request to buy, the method continues at step 302 where the processing module begins to processes the request to buy by verifying information regarding a buyer computing device (e.g., buyer user info and/or info regarding the buyer computing device) associated with the request to buy. The verifying includes one or more of verifying user information associated with the buyer computing device (e.g., buyer user name, buyer account information, buyer PIN, buyer user ID, buyer payment account info, etc.), verifying device information (e.g., buyer device IP address, buyer device serial number, buyer device application identification, etc.) of the buyer computing device, and executing a verification tree process.

When the information regarding the buyer computing device is favorably verified, the method continues at step 304 where the processing module verifies payment information associated with the buyer computing device regarding purchasing of a selected exchange item (e.g., buyer information and exchange item information). The verifying includes one or more of verifying information regarding the selected exchange item (e.g., the EI is still valid, verify balance, verify selling price, selling restrictions, etc.) and verifying buyer payment account information in light of the verified information regarding the selected exchange item (e.g., buyer has sufficient funds, any buying restrictions have been satisfied, buyer financial payment information is valid, etc.).

When the payment information is favorably verified, the method continues at step 306 where the processing module processes payment for the selected exchange item. The processing of the payment for the selected exchange item includes one or more steps. Examples of the steps includes determining a transaction processing fee (e.g., credit card payment fee), determining a commission fee (e.g., flat rate for the marketplace service provider, variable fee based on other factors, may include the transaction processing fee), debiting an account associated with the buyer computing device for the selling price of the selected exchange item, deciding to credit an account associated with the seller computing device for the selling price less the commission fee, and crediting one or more accounts for the transaction processing fee and for the commission fee (e.g., transaction processing fee to credit card affiliate, commission less transaction processing fee to market place operator/service provider).

The method continues at step 308 where the processing module removes the selected exchange item from the digital exchange item marketplace. For example, the processing module updates a database associated with the digital exchange item marketplace to delete an entry associated with the purchased exchange item.

The method continues at step 310 where the processing module adds the selected exchange item to a digital wallet associated with the buyer's computing device. The adding includes, when the digital wallet is active, providing a digital representation of the selected exchange item and exchange item information to the buyer's computer device for display thereon.

FIG. 7 is a flowchart illustrating an example of seller verification for an individual seller 330 within an exchange item marketplace network. The method includes step 332 where a seller's computing device 12 registers with the marketplace network 10 (e.g., with a marketplace server 18 via a network). For example, the seller's computing device registers by issuing a registration request to the marketplace server 18, where the registration request includes one or more of a seller identifier, a seller user device identifier, seller payment information, an identifier of an exchange item for sale, and other information describing the exchange item for sale.

The method continues at step 334 where the marketplace server 18 lists the exchange item for sale. The listing includes updating the virtual marketplace of exchange items to provisionally include an entry for the exchange item for sale, but not display it for sale. The provisional entry of the exchange item includes one or more of the identifier of the exchange item for sale, at least some of the other information describing the exchange item for sale, a balance associated with exchange item for sale, and a discount level associated with exchange item for sale.

The method continues at step 336 where the marketplace server 18 verifies the seller's computing device. The verifying includes one or more of determining whether to allow the seller to sell the exchange item and determining whether to allow the seller's computing device to be utilized in the selling of the exchange item for sale. The method continues to step 338 where, when the seller computing device has been favorably verified, the seller's computing device accepts terms and conditions associated with the offering of the exchange item for sale from the marketplace server.

FIG. 8 is a flowchart illustrating an example of offering an exchange item for sale by an individual seller within an exchange item marketplace network. The method begins or continues at step 350 where a seller's computing device associated with an individual seller accesses an exchange item marketplace network. The method continues at step 352 where the marketplace server 18 determines whether the individual seller has an account with the exchange item marketplace network 10. For example, the marketplace server accesses accounts information to identify an entry associated with the individual seller.

When the individual seller does not have the account, the method continues at step 354 where the marketplace server 18 creates a new entry within the accounts information for the individual user and/or seller user device (e.g., generating the new entry to include one or more of an identifier of the individual seller, an identifier of the seller user device, a personal identification number (PIN), seller payment information, seller address, etc.).

When the individual seller has the account or has just created an account, the method continues at step 356 where the seller's computing device logs in to access to the exchange item marketplace network. The method continues at step 358 where the marketplace server accesses the account information for the individual seller. The method continues at step 360 where the marketplace server determines whether the accessed account information for the individual seller is valid. For example, the marketplace server compares a listed address of the seller to a list of valid addresses. As another example, the marketplace server receives a query response to a query request regarding the seller payment information (e.g., verifying banking information).

When the account information is invalid, the method continues at step 362 where the marketplace server facilitates performing an alternate verification process. The alternate verification process includes one or more of informing an operator to perform a manual verification, verifying another aspect of portions of the seller account information, issuing a verification request to an external entity, and interpreting a received verification response. When the verification was unsuccessful, access to the marketplace is denied.

When the verification was successful, the method continues at step 370 where the seller's computing device provides a brand of an exchange item for sale. For example, the seller user device issues exchange item information to the marketplace server, where the exchange item information includes an identifier of the exchange item for sale and other information associated with exchange item for sale.

The method continues at step 372 where the marketplace server determines whether a brand identifier of the exchange item for sale is valid. For example, the marketplace server compares the brand identifier to a list of valid brand identifiers. As another example, the marketplace server interprets a brand identifier verification response associated with a brand identifier verification request, where the request and response are exchanged with an external entity. As yet another example, the marketplace server indicates that the brand is valid when a received serial number of the exchange item for sale from the seller user device compares favorably to at least one valid serial number associated with the brand.

When the marketplace server determines that the brand identifier is invalid, the method continues at step 376 where the marketplace server attempts to create a valid brand (e.g., establishing a new brand for sale). For example, the marketplace server performs a brand analysis algorithm to produce a brand validity indicator. For instance, the marketplace server issues a brand establishment request to a server associated with establishment of a new brand, receives a brand establishment response, and interprets the brand establishment response to produce the brand validity indicator. When a valid brand cannot be established, the method continues at step 378 where the marketplace server denies the request to sell.

When the brand can be established, the method continues at step 380 where the marketplace server establishes the brand as a valid brand. For example, the marketplace server updates a virtual marketplace of exchange items to include in association of the brand identifier and a valid brand indicator.

With a valid brand, the method continues at step 374 where the seller's computing device provides a personal identification number (PIN) and serial number associated with the exchange item for sale. For example, the seller user device captures an image of the exchange item for sale, sends the captured image to the marketplace server, and the marketplace server interprets the captured image to produce the PIN and serial number. The method continues at step 382 where the marketplace server temporarily stores exchange item information. For example, the marketplace server facilitates storage within the virtual marketplace of exchange items of one or more of the identifier of the exchange item for sale, the serial number of the exchange item for sale, the PIN of the exchange item for sale, the captured image, the brand, the value, and a discount level.

FIG. 9 is a flowchart illustrating an example of seller verification for a bulk seller 400 within an exchange item marketplace network. The method begins or continues at step 402 where the bulk seller registers with the exchange item marketplace network. For example, a bulk seller server associated with the bulk seller's computing device issues a registration request to a marketplace server of the exchange item marketplace network. The registration request includes one or more of an identifier of the bulk seller and/or the computing device, banking information associated with the bookseller, a descriptor of potential bulk exchange items for sale.

The method continues at step 404 where the marketplace server verifies the bulk seller and/or the bulk seller's computing device. The verifying includes one or more of verifying a bulk selling organization and verifying the bulk seller's computing device. For example, the marketplace server performs a credit check on the bulk selling organization. As another example, the marketplace server compares attributes of the bulk seller's computing device (e.g., IP address, access the street, etc.) to expected attributes of the bulk seller's computing device. If not verified, the request is denied.

When the bulk seller is verified, the method continues at step 408 where the bulk seller's computing device uploads bulk file information to the marketplace server. The bulk file information includes one or more of an identifier of the bulk selling organization, an identifier of the bulk seller server, identifiers of the exchange items for sale, and other information associated with the exchange items for sale (e.g., sale price, discount level, serial numbers, personal identification numbers (PINs), etc.). The method continues at step 410 where the marketplace server performs bulk listing of information associated with the bulk file information. For example, the marketplace server adds the exchange items for sale to a virtual marketplace of exchange items.

FIG. 10 is a flowchart illustrating an example of offering an exchange item for sale by a bulk seller within an exchange item marketplace network. The method includes step 420 where a bulk seller's computing device attempts to access an exchange item marketplace network. For example, the bulk seller's computing device issues an access request to a marketplace server of the exchange item marketplace network.

The method continues at step 422 where the marketplace server determines whether the bulk seller has an account with the exchange item marketplace network. For example, the marketplace server accesses accounts information to identify an entry associated with the bulk seller. If not, the method continues at step 424 where the marketplace server creates a new entry within the accounts information for the bulk seller and/or bulk seller's computing device (e.g., generating the new entry to include one or more of an identifier of the bulk seller, an identifier of the bulk seller server, a personal identification number (PIN), bulk seller payment information, bulk seller address, etc.).

When the bulk seller has the account or newly created account, the method continues at step 426 where the bulk seller server logs in to the exchange item marketplace network. The method continues at step 428 where the marketplace server accesses the account information for the bulk seller. The method continues at step 430 where the marketplace server determines whether the accessed account information for the bulk seller is valid. For example, the marketplace server compares a listed address of the bulk seller to a list of valid addresses. As another example, the marketplace server receives a query response to a query request regarding the bulk seller payment information (e.g., verifying banking information).

When the account information is invalid, the method continues at step 432 where the marketplace server facilitates performing an alternate verification process. The alternate verification process includes one or more of informing an operator to perform a manual verification, verifying another aspect of portions of the bulk seller account information, issuing a verification request to an external entity, and interpreting a received verification response. The method continues at step 434 where the marketplace server determines whether the alternate verification process successfully verified the account information associated with the bulk seller. If not, the access request is denied.

When the account information has been verified, the method continues at step 438 where the bulk seller's computing device uploads exchange items for sale. For example, the bulk seller server sends a bulk sale request to the marketplace server, where the bulk sale request includes one or more of identifiers of the exchange items for sale, sale prices, discount levels, serial numbers, personal identification numbers (PINs), etc. The method continues at step 440 where the marketplace server stores exchange item information for the exchange items for sale. For example, the marketplace server stores the identifiers of the exchange items for sale, the sale prices, the discount levels, the serial numbers, the PINs, etc., in a virtual marketplace of exchange items associated with the marketplace server.

FIG. 11 is a flowchart illustrating an example of exchange item verification within an exchange item marketplace. The method includes step 462 where a marketplace server of an exchange item marketplace verifies a personal identification number (PIN) and a serial number of an exchange item for sale. For example, the marketplace server verifies that the serial number conforms to serial number rules associated with a particular brand associated with the exchange item for sale. As another example, the marketplace server verifies that the PIN corresponds to the serial number in accordance with one or more of the serial number rules associated with particular brand and a received serial number verification response (e.g., from an exchange item brand server).

The method continues at step 464 where the marketplace server determines whether the verification is favorable. When the verification is unfavorable, the request to add the exchange item to the marketplace is denied.

When the verification is favorable, the method continues at step 470 where the marketplace server obtains balance and sales price information. For example, the marketplace server receives balance information for the exchange item for sale and a desired price as the sales price information. The marketplace server may utilize seller software tools for setting the sales price. For example, when the user requests automatic price determination, the marketplace server determines at least one of a sales pricing range and a recommended sales price based on one or more of sales history, seller information, potential buyer information, and exchange item availability information.

The method continues at step 474 where the marketplace server performs an exchange item balance check. For example, the marketplace server issues a balance check request to a brand server associated with exchange item for sale, receives a balance check response, and compares a balance received from a seller (e.g., a listed balance) to a balance received from the brand server (e.g., an actual balance), where the balance check request includes one or more of the balance received from the seller, the serial number, and the PIN.

The method continues at step 476 where the marketplace server determines whether the actual balance is substantially equal to zero. If so, the request is denied. If not, the method continues at step 478 where the marketplace server determines whether the actual balance is substantially the same as the listed balance. If not, the method continues at step 480 where the marketplace server updates the exchange item balance (e.g., within a database of the marketplace) to indicate the actual balance.

The method continues at step 482 where the marketplace server determines restrictions (e.g., online only use, in-store only use, etc.) of the exchange item for sale. The determining may be based on one or more of a predetermination, accessing the database of the marketplace, and interpreting a restrictions query response from the brand server. The method continues at step 484 where the marketplace server determines whether the restrictions inhibit sale of the exchange item in the marketplace. The determining includes comparing circumstances of selling exchange items within the marketplace with the restrictions to produce a comparison and interpreting the comparison to determine whether the sale is prohibited. For example, the marketplace server indicates that the sale is prohibited when detecting that a particular restriction associated with the exchange item prohibits the sale by the seller (e.g., unauthorized seller). If so, the request is denied. If not, the method continues at step 486 where the marketplace server approves the exchange item for the marketplace and stores exchange item information (e.g., brand identifier, serial number, PIN, barcode information, exchange item image, actual balance, and the restrictions).

FIG. 12 is a flowchart illustrating an example of adding and/or removing an exchange item within an exchange item marketplace network. The method includes step 502 where a marketplace server of the exchange item marketplace network creates a digital representation of an exchange item for sale. For example, the marketplace server captures a digital image of a front and back of a gift card exchange item and interprets the captured digital image to produce exchange item information (e.g., brand, value, serial number).

The method continues at step 504 where the marketplace server adds the exchange item (EI) to a database (DB) of the marketplace (MP). For example, the marketplace server inserts a new entry into a sorted list of other previously entered exchange items within the database associated with the brand, where the new entry includes the brand, the value, the serial number, and a price (e.g., a discounted price as compared to the value).

The method continues at step 506 where the marketplace server determines whether to update sales price for the exchange item within the database. The determining may be based on one or more of a request and a market efficiency pricing algorithm output. For example, the marketplace server receives a request from a seller associated with the exchange item to change the price. As another example, the marketplace server executes a market efficiency pricing algorithm to produce an indication that the price should be changed to improve the efficiency of the marketplace. If the price is to be updated, the method continues at step 508 where the marketplace server changes the sales price accordingly. The method continues at step 510 where the marketplace server updates the exchange item information in the database of the marketplace.

If the price is not being updated or after the price has been updated, the method continues at step 512 where the marketplace server determines whether the exchange item has been selected for purchase. If not, the method continues at step 514 where the marketplace server determines whether the offer to sell the exchange item has been withdrawn (e.g., interpreting a request from the seller, in accordance with a withdraw protocol, accessing the database). If yes, the method continues at step 516 where the marketplace server removes the exchange item from the database (e.g., database update to remove the entry associated with exchange item). If not, the method repeats at step 506.

When the exchange item has been selected for purchase, the method continues at step 518 where the marketplace server marks the exchange item as selected for purchase. For example, the marketplace server updates an entry of the marketplace database to indicate that the exchange item has been selected for purchase, but not yet sold. The method continues at step 520 where the marketplace server determines whether the sale has been finalized. The determining may be based on one or more of confirming payment from a purchaser, confirming payment to the seller, and confirming payment to another payee (e.g., a commission to a market place operator). When the sale is finalized, the method continues at step 522 where the marketplace server removes the exchange item from the market database (e.g., removes the entry associated with the exchange item from the database), records sale of the exchange item (e.g., notifies a seller of the purchase), adds the exchange item to the buyer's e-wallet, and proceeds to a payment process (e.g., to collect payment from the purchaser).

When the sale is not finalized (e.g., still pending approval of the buyer's financial information), the method continues at step 524 where the marketplace server determines whether the sale is to be voided. The determining may be based on one or more of detecting an unfavorable payment condition, receiving a sale voided request, and detecting an estimated fraud level that compares unfavorably to a fraud threshold level. If the sale is to be voided, the method continues at step 526 where the marketplace server undoes the marking of the as selected for purchase (e.g., database updated to reflect that the exchange item is available for sale). The method then repeats at step 506.

When the sale is not to be voided, the method continues at step 528 where the marketplace server determines whether another request to purchase another exchange item has been received (e.g., a request purchase, the same exchange item or a similar exchange item). If not, the method repeats at step 520.

When another request to purchase the exchange item has been received, the method continues at step 530 where the marketplace server determines whether the marketplace includes another equivalent exchange item (e.g., performs a database search). If not, the method repeats at step 520. If yes, the method continues at step 532 where the marketplace server marks the equivalent exchange item as selected for purchase and processes the purchase accordingly. The method branches to step 520 to finalize both pending sales.

FIG. 13 is a flowchart illustrating an example of buyer verification and exchange item purchase verification within an exchange item marketplace. The method includes step 552 where a buyer's computing device accesses the exchange item marketplace. For example, the buyer's computing device sends a registration request to the marketplace server. The registration request includes one or more of an identifier of the buyer, an identifier of the buyer user device, payment information associated with the buyer, a security credential, and other buying information (e.g., buying history, buying preferences, buying terms and conditions, etc.). The method continues at step 554 where the marketplace server determines (e.g., database access) whether the buyer has an account the marketplace. If not, the method continues at step 556 where the marketplace server determines whether to allow the buyer to proceed as a guest. The determining may be based on one or more of a system security level, a fraud detection algorithm fraud level indicator, a comparison of the fraud level indicator to a fraud threshold level, a request, a predetermination, a marketplace activity indicator, and a marketplace efficiency indicator.

If the buyer is allowed to access the system as the guest, the method continues at step 558 where the marketplace server collects the buyer's information (e.g., information contained the request and any other information to support the buyer functioning as a guest in the marketplace), and may, based on the buyer's information, enable the buyer to further access the marketplace to purchase an exchange item. If the buyer is not allowed to access the system as the guest, the method continues at step 560 where the marketplace server creates an account for the buyer (e.g., adds a new entry in the database). The creating of the account may include obtaining further information from the buyer.

When the buyer has an account or after the account is created, the method continues at step 562 where the buyer logs into the marketplace (e.g., accesses the marketplace network). The method continues at step 564 where the marketplace server accesses account information for the buyer (e.g., retrieves buyer information from the database).

The method continues at step 566 where the marketplace server determines whether the buyer is a valid buyer. For example, the marketplace server compares one or more aspects of the buyer information to expected values of the one or more aspects to produce a comparison and interprets the in light of a desired pattern for the comparison. For instance, the marketplace server utilizes a decision tree structure to interpret a plurality of fraud detection questions to provide a plurality of fraud detection answers and to interpret the plurality of fraud detection answers to indicate whether the buyer is valid.

When the buyer is invalid, the method continues at step 568 where the marketplace server performs an alternate verification process (e.g., facilitating manual interpretation of risk factors by an operator associated with the market place network, invoking a secondary fraud detection algorithm). The method continues at step 570 where the marketplace server determines whether the alternate verification process is successful. If not, the buyer's access to the marketplace is denied.

If the buyer is validated, the method continues at step 582 where the marketplace server facilitates display of brands of exchange items available for purchase. For example, the marketplace server sends marketplace inventory information (e.g., brands, values, discount levels, etc.) to the buyer's computing device for display thereon. The method continues at step 584 where the marketplace server receives a brand selection from the buyer's computing device.

The method continues at step 586 where the marketplace server facilitates display of exchange items associated with the selected brand. For example, the marketplace server sends marketplace inventory information associated with the selected brand to the buyer's computing device for display thereon (e.g., displaying various available balances and discount levels for exchange items of the brand). In addition, the marketplace server provides the buyer's computing device with exchange item information of related brands to the selected brand (e.g., selected a particular coffee shop, provide exchange items from multiple coffee shops).

The method continues at step 588 where the marketplace server receives a selection of an exchange item for purchase from the buyer's computing device. For example, the buyer's computing device sends the server a message that includes one or more of the ID of the exchange item, the brand(s) of the exchange item, a descriptor of the exchange item, a value of the exchange item, a purchase price of the exchange item, a desired purchase price of the exchange item, a range of a desired purchase price of the exchange item, a serial number associated with exchange item, and/or buyer payment information.

The method continues at step 590 where the marketplace server adds the selected exchange item to a cart associated with the buyer (e.g., update a temporary list of one or more exchange items for purchase). The method continues at step 592 where the marketplace server determines whether the buyer intends to keep shopping. The determining may be based on one or more of detection of the expiration of a shopping timer, receiving an indicator that buyer is still shopping, receiving an indicator that the buyer has finished shopping. If yes, the method repeats at step 582.

When buyer desires to checkout, the method continues at step 594 where the marketplace server determines whether valid payment has been obtained. The determining includes at least one of verifying a complete payment (e.g., verifying a credit card transaction, etc) and verifying that the buyer is capable of providing full payment (e.g., verifying purchase ability on a buyer credit card). If not, the order is voided. Alternatively, the method branches from step 564 to step 582 to perform the steps 582-592, such that steps 566-570 to validate the buyer are performed after step 592 and before step 594.

If a valid payment is received, the method continues at step 598 where the marketplace server determines whether a balance of each selected exchange item is accurate (e.g., a balance listed in the database matches a balance check response from a brand server associated with the exchange item). If the balance is not accurate, the transaction is voided. Note that it may be restarted with adjustments made based on the accurate balance.

If the balance is accurate, the method continues at step 600 where the marketplace server adds the exchange item to a buyer wallet (e.g., the marketplace server sends exchange item information to the buyer user device). The method continues at step 602 where the marketplace server continues to proceed to payment to conclude collection of payment from the buyer if not already collected and to distribute payment to one or more payees (e.g., the seller, other payees).

FIG. 14 is a flowchart illustrating an example of exchange item payment within an exchange item marketplace. The method includes step 622 where a marketplace server associated with exchange item marketplace receives funds from a buyer's financial server for payment of a selected exchange item for purchase. For example, the marketplace server verifies that a credit card payment shall be made to compensate for purchase of the selected exchange item.

The method continues at step 624 where the marketplace server determines whether a refund is to be processed for the payment of the exchange item for purchase. The determining may be based on one or more of receiving a transaction cancellation request after the funds have been received for payment, detecting that an estimated fraud level is greater than a fraud threshold level, and interpreting at least one of a seller or buyer terms and conditions to trigger the refund.

If a refund is to be made, the method continues at step 626 where the marketplace server processes the refund (e.g., reverse a credit card payment from the buyer). The method continues to step 628 where the marketplace server adds the selected exchange item back to the marketplace for sale (e.g., re-creates an entry to include the exchange item information and stores the entry in a database associated with the exchange item marketplace).

If a refund is not being made, the method continues at step 630 where the marketplace server determines whether a payment adjustment is to be processed when the refund is not to be processed. The determining may be based on one or more of interpreting seller terms and conditions, buyer terms and conditions, network operator terms and conditions, and other payee's terms and conditions. For example, the marketplace server interprets terms and conditions of a credit card company associated with the buyer that indicates that a 3% fee is required. If an adjustment is required, the method continues at step 632 where the server processes the adjustment. If no adjustments are to be made or after the adjustment is made, the method continues at step 634 where the marketplace server calculates a commission for the network operator and/or other payees in accordance with terms and conditions associated with payment resolution. For example, the marketplace server subtracts the 3% credit card fee from a gross commission rate of 15% for the network operator to produce a net commission rate of 12% for the network operator. The method continues at step 636 where the marketplace server adds the seller's funds to a seller's e-wallet. The adding includes at least one of indicating a marketplace credit, indicating a cash payment, indicating a payment in accordance with payment information for the seller, and indicating another exchange item as compensation for the seller. The method continues at step 638 where the marketplace server notifies the seller of funds in the seller's wallet. For example, the marketplace server sends a seller wallet update to a seller user device, where the seller wallet update includes an indication of the funds to be added the seller's wallet.

The method continues at step 640 where the marketplace server determines whether a funds withdraw request has been received from the seller's computing device. If not, the method continues at step 646 where the server determines whether it is receiving a purchase request from the seller's computing device, which is now functioning as a buyer's computing device. If not, the method repeats at step 640.

When a funds withdraw request is received, the method continues at step 642 where the marketplace server sends funds to the seller's financial server. For example, the marketplace server sends and automatic clearinghouse (ACH) transfer of funds to the seller's financial server in accordance with seller payment information. The method continues at step 644 where the marketplace server updates the seller's wallet. For example, the marketplace server sends a further update to the seller user device indicating that the seller's wallet has been updated to include the payment.

When a purchase request is received, the method continues at step 648 where the marketplace server processes the purchase request. For example, the marketplace server indicates that the selected other exchange item has been removed from the marketplace and transferred to the seller's wallet. The method continues at step 650 where the marketplace server updates the seller's wallet to debit the amount of the purchase just processed.

FIG. 15 is a flowchart illustrating a method that includes step 660 where a marketplace server determines whether a new exchange item is to be added to a buyer wallet associated with the buyer user device. The determining may be based on one or more of processing a purchase request for the new exchange item, obtaining a favorable purchase response to a purchase request for the new exchange item, and receiving a payment response indication that includes the new exchange item as compensation.

If a new exchange item is to be added to the buyer's e-wallet, the method continues at step 662 where the marketplace server and/or the buyer's computing device creates and stores a digital representation of the exchange item. The creating of the digital representation includes at least one of capturing a digital image of the exchange item, interpreting the captured image to produce attributes (e.g., brand, brand logo, serial number, barcode, etc.) of the exchange item, and receiving the attributes of the exchange item. The method continues at step 664 where the buyer's computing device and/or the marketplace server creates and stores an exchange item file, where the file includes the digital representation of the exchange item and other information regarding the exchange item.

The method continues at step 666 where the buyer's computing device determines whether the buyer's wallet is activated (e.g., status check, interpret a query). If not, the method repeats at step 660. If the wallet is activated, the method continues to step 668 where the buyer's computing device displays the buyer wallet and wallet navigation information (e.g., tools to facilitate searching a plurality of digital representations of the exchange items associated with the buyer wallet). The method continues at step 670 where the buyer's computing device determines whether an exchange item has been selected for utilization (e.g., to spend down a gift card when the exchange item is the gift card). If not, the method continues at step 672 where the buyer's computing device determines whether the wallet has been deactivated. If deactivated, the method ends. If not deactivated, the method repeats at step 660.

When an exchange item has been selected, the method continues at step 674 where the buyer's computing device determines whether use of the selected exchange item will be via a mobile scan payment (e.g., displaying a bar code of the exchange item on a display of the buyer's computing device). If yes, the method continues at step 676 where the buyer's computing device displays a bar code of the exchange item and, at step 680, the bar code is read by point of sales equipment of a merchant to execute a purchase.

If mobile scan pay is not being used, the method continues at step 678 where the buyer's computing device displays the exchange item file (e.g., including a unique serial number associated with the exchange item). The displaying of the exchange item file facilitates manual reading of the unique serial number by an operator of the point-of-sale terminal or similar to facilitate utilization of the exchange item to execute a purchase.

The method continues at step 680 where the buyer's computing device determines whether the exchange item use has been successfully executed to make a purchase. The determining may be based on one or more of interpreting a payment confirmation indicator, receiving a purchase verification, and receiving an indicator that at least a portion of an available balance associated with the exchange item for use has been utilized. If yes, the method continues at step 682 where the buyer's computing device updates balance information in the exchange item file. For example, the buyer user device subtracts a point-of-sale purchase amount from a previous balance of the exchange item to produce an updated balance.

If the use of the exchange item was not executed, the method continues at step 684 where the buyer's computing device determines whether the unsuccessful use of the exchange item to execute a purchase was due to an error of the exchange item. The error may be an expired exchange item, insufficient balance on the exchange item, a violated restriction, etc. If it is not an error (e.g., a denial by the POS equipment), the method continues at step 688 where the transaction is terminated and the method repeats at step 668.

If it is an error, the method continues at step 686 where the buyer's computing device updates the exchange item file based on the exchange item error. For example, the buyer user device updates the exchange item file correct the balance when the balance mismatch has been indicated. FIG. 16 is a schematic block diagram of another embodiment of an exchange item marketplace network 10A that includes a plurality of sellers 702, a plurality of buyers 704, and an on-line exchange item marketplace 700. The sellers 702 include individual sellers 706, bulk sellers 708, and retailers 710. The buyers 704 include individual buyers 712 and other types of buyers 714 (e.g., bulk buyers, resale buyers, etc.). Each seller 702 and each buyer 704 corresponds to a computing device 12-16 that includes a marketplace interface module 716 that enables the computing device access to the marketplace 700 and to function therein. The marketplace interface module 716 includes a browser application 722, a mobile device application 720, and/or any type of application that enables access to the marketplace 700. The computing core 52 of the user device executes one or more of these applications. For instance, each of the applications includes operational instructions that are stored in memory (e.g., main memory, flash memory, SS memory, HD memory, and/or cloud memory) and executed by the processing module 62 of the computing core 52.

Alternatively, the marketplace interface module 716 includes a processing circuit and memory, wherein the memory stores and the processing circuit executes the operational instructions of the application. As yet another alternative, the processing circuit of the marketplace interface module 716 and the processing module 62 of the computing core 52 co-process the operational instructions of one or more of the applications. Interface 718 functions in a similar manner to provide bulk resellers 708 and/or retailers 710 access and function within the marketplace 700.

One or more marketplace servers 18 supports the online exchange item (EI) marketplace 700 by performing the functions of the corresponding functional blocks. The functional blocks include seller software tools 738, individual seller fraud detection 724, individual sale processing 726, bulk seller verification processing 730, bulk sale processing 732, retailer verification processing 734, retailer sale processing 736, displaying exchange items for sale 728 in the marketplace 700, payment processing 748, MP user e-wallet 750, buyer fraud detection 740, purchase processing 742, consumer profiles 744, and market customization 746. A functional block includes one or more of a standalone processing module that executes operational instructions to perform the corresponding functions of the block, a software algorithm executed by the computer core of the server to perform the corresponding functions of the block, and/or a combination thereof. The server(s) 18 perform the marketplace user e-wallet functional block 750 to create and maintain an e-wallet for a user of the marketplace 700. The e-wallet is essentially a file for an individual user (e.g., a person, a legal entity, etc.) that stores information regarding exchange items bought, sold, and/or used by the user. For example, the e-wallet stores a digital representation of each purchased exchange item that has a value greater than zero. For example, a digital representation of a gift card is displayed in an asset section of the e-wallet while the gift card has a balance above zero and the gift card has not expired. When the balance is zero or the gift card expires, the digital representation is removed and the information regarding the gift card is stored in an archive section of the e-wallet.

The e-wallet is further capable of storing and tracking marketplace credit. For example, a user may purchase marketplace credit that is subsequently used to purchase an exchange item. In addition, a seller of an exchange item may be paid in marketplace credit that the seller may use to purchase an exchange item or cash out.

The e-wallet further functions to archive data regarding previous exchange item purchases and/or previous exchange item sales. The amount of data stored for each exchange item purchase or sale may be user defined or set based on a system default setting. For example, the data for a purchase includes one or more of a purchase price, the exchange item ID, a serial number, a brand name, a purchase date, the value of the exchange item, restrictions of the exchange item, and an expiration date. The data for a purchased exchange item may further include use information (e.g., when the exchanged item was used, the amount of value used, the date of use, the place of use, etc.) and/or remaining value information.

As another example, the data for a sale includes one or more of an asking selling price, a sold price, the exchange item ID, a serial number, a brand name, an offer for sale time stamp, a sold time stamp, the value of the exchange item, restrictions of the exchange item, and an expiration date. The data for a sold exchange item may further include price reduction information (e.g., the amount of the change, a change time stamp, etc.) and/or information regarding a withdrawal of an offer for sale.

The server(s) 18 perform the seller software tools functional block 738 to assist a seller (e.g., individual, bulk, or retailer) in setting a price for an exchange item. For example, the server(s) 18 record data regarding exchange items offered for sale, data regarding purchases of exchange items, and data regarding exchange items for which the offer for sale was withdrawn. From this data, the server(s) 18 determines predictive sales information. For example, the server(s) 18 determines for a particular type of exchange item (e.g., a gift card for a particular franchise) a correlation between the value of the exchange item and duration in the marketplace (e.g., a $250 gift card has an average duration of 1 day, a $100 gift card has an average duration of 12 hours, a $50 gift card has an average duration of 5 hours, etc.).

As another example of predictive sales information, the server(s) 18 determine a correlation between sales price and duration in the marketplace (e.g., a 5% discount has an average duration of 12.5 hours, a 3% discount has an average of 1 day, and a 10% discount has an average duration of 1.5 hours). As yet another example, the server(s) 18 determine a periodic sales volume for a particular exchange item (e.g., how many sold in an hour, six hours, a day, etc.). As yet another example, the server(s) 18 determine a current quantity of the particular exchange items for sale (e.g., how many are currently being offered for sale, at what sales price, the current average duration in the marketplace, etc.). The server(s) 18 may further analyze any type of data maintained by the system 10A to assist in the creation of predictive sales information.

In addition to creating the predictive sales information, the server(s) 18 generate a seller's profile, which includes information regarding the sales tendencies and/or preferences of a particular seller. For example, the seller's profile includes information regarding one or more of the types of exchange items offered for sale, information regarding if and when exchange item offers for sale are withdrawn, initial asking prices for exchange items offered for sale, actual sales price information and corresponding discounted percentage, frequency for which initial asking price is adjusted, average duration of exchange items in the marketplace, standard deviation of duration of exchange items in the marketplace, etc.

From the predictive sales information and the seller's profile, the server(s) 18 provide a suggested sales price for a particular exchange item. For example, the seller profile indicates that the seller has a tendency to offer a particular exchange item with a minimal discount and prefers that the exchange item remain in the marketplace for less than 6 hours. Further, the predictive sales information for the particular exchange item indicates that there is currently above normal quantity of the exchange item for sale, the current asking price has a greater discount than the seller's preference, and the current average duration in the marketplace is 7 hours, the server(s) 18 provides one or more recommendations and corresponding predictive outcomes (e.g., an initial asking price below the seller's profile to sell the exchange item within 6 hours, an initial asking price corresponding to the seller's profile to sell the exchange item within 11 hours, etc.). The server(s) 18 may further provide the predictive sales information to the seller's computing device.

The server(s) 18 perform the individual seller fraud detection functional block 724 to automate detection of a fraudulent seller and/or a fraudulent exchange item. This includes the seller verification and the exchange item verification as discussed in one or more of FIGS. 6A-6D, 7-11, 18A, and 18B. The fraud detection further includes an automated process for resolving a potential fraud issue. For example, when a verification of seller falls between verified and not verified, the server(s) 18 evoke a process to render a definitive verification decision. As another example, when the verification of an exchange item falls between verified and not verified, the server(s) 18 evoke a process to render a definitive verification decision.

To extend the use of the marketplace to retailers or branded companies (i.e., the entity that initiates a gift card and ultimately accepts the gift card as payment), the server(s) 18 perform the retailer verification processing functional block 734 and the retailer sale processing functional block 736. The retailer verification processing functional block 734 includes one or more of setting up an account for a retailer to sell exchange items via the marketplace, verifying the retailer at least at the set up of the account and potentially for each transaction conducted via the marketplace, verifying the exchange items being offered for sale, and/or other verification mechanisms. As an example, a secure portal is established between the retailer seller and the marketplace server(s) 18 such that any communications via the secure portal is at least initially deemed a valid communication.

The retailer sale processing functional block 736 includes one or more of creating digital representations of the exchange items offered for sale, determining selling parameters and posting the digital representations and the parameters in the marketplace. The selling parameters include one or more of sales price, listing duration before changing price, restrictions, withdraw procedures, etc.

The server(s) 18 perform the buyer fraud detection functional block 740 to automate detection of a fraudulent buyer and/or fraudulent financial information used for purchasing. This includes the buyer verification and the purchase verification as discussed in one or more of FIGS. 5, 6A-6D, 13, and 20A-20D. The fraud detection further includes an automated process for resolving a potential fraud issue. For example, when a verification of buyer falls between verified and not verified, the server(s) 18 evoke a process to render a definitive verification decision. As another example, when the verification of financial information falls between verified and not verified, the server(s) 18 evoke a process to render a definitive verification decision.

The server(s) 18 perform the payment processing functional block 748 to process payment through the user e-wallets of the seller and of the buyer. For instance, payment by the buyer is made from the buyer's e-wallet by debiting a credit card, a checking account, a savings account, a currency balance (e.g., money on account for purchases), and/or marketplace credit. Payment to the seller is made by crediting the seller's e-wallet with currency, marketplace credit, and/or some form of financial receipt. The mechanics of the payment process include the functionality described in one or more of FIGS. 5, 6A-6D, 11-14, and 20A-20D.

The server(s) 18 perform the consumer profiles functional block 744 for a buyer. For the buyer, its consumer profile includes data regarding exchange item purchases of the buyer. The data includes one or more of the exchange items purchased, frequency of purchases, average purchase price, average value of purchased like exchange items (e.g., coffee shop gift cards), preferred discounts, etc. Note that this may be included in the buyer's e-wallet or maintained as a separate file.

The server(s) 18 perform the market customization functional block 746 to customize marketing of exchange items being offered for sale to particular buyers based on their buyer profiles. The market customization functional block 746 further includes determining a type and a quantity of exchange items a retailer should offer for sale and directing marketing efforts to a particular segment of buyers. In this manner, the system 10A efficiently and effectively couples exchange items for sale to buyers who typically buy such exchange items.

The server(s) 18 perform the individual sales processing function block 726, the bulk seller verification processing functional block 730, the bulk sale processing functional block 732, and the purchase processing functional block 742 as described with reference to one or more of FIGS. 2, 5, 6A-6D, 7-10, 18A, and 18B. The server(s) 18 also perform the displaying exchange items for sale functional block 728 to add/remove/edit an exchange item in the marketplace 700 as described with reference to one or more of FIGS. 2, 5, 6A-6D, 7-10, 12, and 17A-21B.

FIG. 17A is a schematic block diagram of another embodiment of an exchange item marketplace network that includes the seller's computing device 12 and the marketplace (MP) server(s) 18, which includes a processing module 802. The seller's computing device 12 and the MP server(s) 18 may be operably coupled with the network(s) 24. The database 20 stores the virtual marketplace of exchange items 22 and transaction history 804.

In an example of operation of the pricing of the exchange items, the processing module 802 receives exchange item (EI) information 806 from the seller's computing device 12 (e.g., from the mobile app 198, from an input via the web browser 196) for an exchange item for sale. The EI information 806 includes one or more of an EI type indicator (e.g., gift card, store credit, voucher, etc.), a brand identifier, a balance, a personal identification number (PIN), a serial number, an expiration date, a seller identifier (ID, a desired selling price, a desired net price (e.g., actual selling price less all commissions and fees), and a desired pricing approach (e.g., fixed specified price, market-based, auto pricing, an auto pricing approach, i.e., as suggested by the MP server 18, based on an input, etc.).

Having received the EI information 806, the processing module 802 obtains inventory information 808 by retrieving a portion of the virtual marketplace of exchange items 22 inventory information from the database 20. For example, the processing module 802 accesses the database 20 based on the brand of the EI information 806 to identify the portion of the virtual marketplace of exchange items 22 that corresponds to the brand. The portion may identify one or more exchange items associated with the brand. The inventory information 808 includes one or more of the brand, a balance, a price, an expiration date, availability volume, pricing rules for the brand, and exchange item utilization rules for the brand. For example, the processing module 802 retrieves inventory information 808 identifying available gift cards Al-AG when the brand of the EI information 806 is brand A and the EI type of the EI information 806 is gift card.

Having obtained the inventory information 808, the processing module 802 identifies transaction history 810 corresponding to the EI information 806. The identifying includes the processing module 802 retrieving at least a portion of the transaction history 804 from the database 20 to produce the transaction history 810, where the retrieved portion is associated with the brand and may further be associated with exchange items of the brand and similar balance information. The transaction history 810 includes one or more records of sales of similar exchange items to the exchange item for sale and may further include one or more summaries (e.g., volume sold by price range and timeframe) of two or more records of sale. Each record of sale includes one or more of a sold EI type indicator, a sold brand, a sell price, a balance, a discount level, a commission level, a fee level, a date, a timestamp, a seller identifier, a buyer identifier, a selling season indicator, a special sale indicator, etc. For example, the processing module 802 retrieves a portion from the transaction history 804 that identifies sell pricing of a last 10 transactions and a last month of transactions of sold gift cards of the indicated brand associated with a similar balance as the indicated balance of the EI information 806.

Having identified the transaction history corresponding to the EI information, when the pricing approach is the auto pricing approach, the processing module 802 determines a selling price. The determining includes one or more of selecting a particular auto-pricing approach of a plurality of auto-pricing approaches, generating the selling based on the selected pricing approach and one or more of the EI information 806, the inventory information 808, the transaction history 810, and the pricing rules associated with the brand. The selecting of the auto-pricing approach may be based on one or more of a predetermination, a pricing approach indicator of the EI information 806, another request, system registry information associated with the database 20, and an input from a system operator of the exchange item marketplace network.

The auto-pricing approaches include calculating an average selling price on a last group of sold exchange items that compare favorably to the exchange item for sale (i.e., an average selling price of a last five sold exchange items that compare favorably to the exchange item for sale), calculating an average selling price of exchange items sold during a time frame (e.g., a last n days, a number of days of a similar seasonal timeframe of a previous year), i.e., an average selling price of exchange items sold during the last 30 days that compare favorably to the exchange item for sale, calculating the selling price based on available inventory of similar exchange items (e.g., a.k.a. supply and demand pricing), and calculating the selling price to optimize an aspect of market efficiency of the exchange item marketplace network (e.g., to facilitate optimization of transaction volume).

Having produced the selling price, the processing module 802 issues pricing guidance 812 to the seller's computing device 12. The pricing guidance 812 includes one or more of a representation of the inventory information 808 (e.g., a subset associated with the indicated brand), a representation of the transaction history 810 (e.g., a selected subset associated with recent sales of similar exchange items), a pricing range based on the transaction history 810 and the selling price, and the selling price (e.g., suggested auto-pricing level). For example, the processing module 802 generates the pricing guidance 812 and sends the pricing guidance 812 to the seller's computing device 12 for display and feedback.

Having sent the pricing guidance 812 to the seller's computing device 12, the processing module 802 receives pricing confirmation 814 from the seller's computing device 12, where the seller's computing device 12 generates the pricing confirmation 814 to include at least one of an acknowledgment of the selling price, a new desired selling price when the selling price is unacceptable, preconditions to enable the new desired selling price, a market price indicator (e.g., sell immediately at a substantially identical price to a last similar exchange items sold), and acknowledgment of the auto pricing process. When receiving the pricing confirmation 814 that includes the new desired selling price, the processing module 802 establishes the selling price for the exchange item for sale at the desired selling price level in accordance with the pricing rules for the brand (e.g., allowing the desired selling price if within an allowable range, etc.).

Having received the pricing confirmation 814, the processing module 802 updates the virtual marketplace of exchange items 22 to include priced exchange item information 816. The priced exchange item information 816 includes one or more of the brand, the balance, the pin, the serial number, expiration date, the seller identifier, the selling price, the selling preconditions, and the pricing rules. For example, the processing module 802 generates a new entry for the virtual marketplace of exchange items 22 and stores the new entry in the database 20 such that the exchange item for sale becomes visible to buyers.

FIG. 17B is a flowchart illustrating an example of pricing exchange items within an exchange item marketplace network that is executed by a server and/or a computing device. The method includes step 830 where a processing module of the server and/or computing device receives exchange item (EI) information from a seller's computing device. For example, the processing module receives qualified EI information that may include a verified serial number for a verified brand.

The method continues at step 832 where the processing module obtains inventory information from EI virtual marketplace that corresponds to the EI information. For example, the processing module accesses the EI virtual marketplace based on the verified brand to identify similar exchange items and retrieves inventory information associated with the similar exchange items.

The method continues at step 834 where the processing module identifies transaction history corresponding to the EI information. For example, the processing module accesses transaction history to identify transactions associated with the verified brand and retrieves historical information of the identified transactions. When a pricing approach includes auto-pricing, the method continues at step 836 where the processing module determines a pricing value based on one or more of the EI information, the inventory information, and the transaction history. For example, the processing module determines a particular auto-approach and calculates the pricing value utilizing the particular auto-approach.

The method continues at step 838 where the processing module issues pricing guidance to the seller user device. The pricing guidance includes one or more of a representation of the inventory information, a representation of the transaction history, and the pricing value. For example, the processing module generates the pricing guidance and sends the pricing guidance to the seller user device.

The method continues at step 840 where the processing module receives pricing confirmation from the seller user device, where the seller user device generates the pricing confirmation to include at least one of an acknowledgment of the pricing value and an alternative desired selling price. The method continues at step 842 where the processing module updates the EI virtual marketplace to include EI information. For example, the processing module stores a new entry that includes one or more of the verified brand, the verified balance, a pin, a serial number, and expiration date, a seller identifier, the pricing value (e.g., selling price), and any associated pricing rules.

FIG. 18A is a schematic block diagram of another embodiment of an exchange item marketplace network that includes the seller's computing device 12 and the marketplace (MP) server(s) 18. The MP server(s) 18 includes a processing module 862 and is coupled to the database 20.

In an example of operation of the verifying of the seller, the processing module 862 receives seller information 866 from the seller's computing device 12, where the seller's computing device 12 is associated with a proposed exchange item for sale. The seller information 866 includes one or more of a user identifier (ID), user payment information (e.g., credit card information, bank account information, PayPal™ information, Apple Pay™ information, etc.), user street address, user personal identification number (PIN), user account activity history, user device browser history, etc. For example, the processing module 862 receives the seller information 866 as new account information when the seller's computing device 12 accesses the MP server(s) 18 a first time. As another example, the processing module 862 retrieves at least a portion of the seller information 866 from the database 20 when the seller's computing device 12 was previously accessed the MP server(s) 18.

Having received the seller information 866, the processing module 862 obtains user account information 868 corresponding to the seller's user device 12. For example, the processing module 862 accesses database 20 to retrieve a portion of the user accounts 864 as the user account information 868, where the retrieved portion corresponds to the seller's user device 12. The user account information 868 includes one or more of a user identifier, user payment information (e.g., credit card information, bank account information, PayPal™ information, Apple Pay™ information, etc.), user street address, user PIN, account activity history, a virtual account balance within the marketplace, a record of exchange item purchases, etc.

Having obtained the user account information 868, the processing module 862 obtains inventory information 808 corresponding to the proposed exchange item for sale. For example, the processing module 862 retrieves, from the database 20, a portion of the virtual marketplace of exchange items 22 to extract the inventory information 808, where the portion is associated with the proposed exchange item for sale (e.g., same brand, similar balance).

Having obtained the inventory information 808, the processing module 862 selects a seller verification approach from a plurality of seller verification approaches. The plurality of seller verification approaches includes validating a street address, determining whether associated account activity history is favorable, verifying seller payment information (e.g., verifying bank information), verifying that history of the web browser 196 compares favorably to a predetermined browser profile and/or a historical profile for the seller's computing device 12, etc.

The selecting of the seller verification approach may be based on one or more of utilizing a predetermined approach, utilizing an approach associated with the seller's computing device 12, determining a risk level based on one or more of the seller ID, the brand associated with the proposed exchange item for sale, account activity history of the user account information, and mapping the risk level to a particular seller verification approach. For example, the processing module 862 determines to utilize the approach to verify that the history of the web browser 196 compares favorably to the historical profile for the seller's computing device 12 when the historical profile has matched a common profile for the seller's computing device 12 for the last 24 months.

Having selected the seller verification approach, the processing module 862 applies the selected seller verification approach to the seller information 866 utilizing the user account information 868 and the inventory information 808 to produce a seller verification status 870 (e.g., approved seller status, disapproved seller status, conditional approval status, i.e., limited to a particular brand and particular balance range). For example, the processing module 862 verifies the street address for the seller's user device, then verifies credit card information, and then verifies that the browser history compares favorably to a predetermined profile of the seller associated with selling of previous exchange items of the brand.

Having produced the seller verification status 870, the processing module 862 indicates the seller verification status 870. For example, the processing module 862 sends the seller verification status 870 to the seller's computing device 12 and updates the user accounts 864 to include a historical record entry of the seller verification status for this instance of verification.

FIG. 18B is a flowchart illustrating an example of verifying a seller within an exchange item marketplace network that is performed by a server and/or a computing device. The method begins or continues at step 880 where a processing module of the server and/or computing device receives seller information from a seller's computing device associated with the proposed exchange item for sale. The receiving may include one or more of receiving as part of new account information and retrieving user account information from a database as the seller information.

The method continues at step 882 where the processing module obtains user account information corresponding to the seller user device. For example, the processing module accesses the database to retrieve the user account information from a user accounts portion of the database. The method continues at step 884 where the processing module obtains inventory information corresponding to the proposed exchange item for sale. For example, the processing module retrieves the inventory information from a virtual marketplace of exchange items of the database and extracts pricing rules for a brand associated with the proposed exchange item for sale.

The method continues at step 886 where the processing module selects a seller verification approach. The selecting includes one or more of determining a risk level based on one or more of seller identity, the brand associated with the proposed exchange item for sale, and account activity history associated with the user account information, and mapping the determined risk level to an approach of a plurality of verification approaches.

The method continues at step 888 where the processing module applies the selected seller verification approach to the seller information utilizing the user account information in the inventory information to produce a seller verification status. For example, the processing module applies one or more steps associated with one or more approaches of the selected seller verification approach to produce the seller verification status. The method continues at step 890 where the processing module indicates the seller verification status. For example, the processing module sends the seller verification status seller user device and updates the user accounts to include a history record of the seller verification status.

FIGS. 19A and 19B are schematic block diagrams of another embodiment of an exchange item marketplace network that includes buyer's computing devices 1-2 and marketplace (MP) server(s) 18. The MP server(s) 18 includes a processing module 902 and is coupled to the database 20.

FIG. 19A illustrates steps of an example of operation of the selecting of the exchange item for purchase where the processing module 902 receives an exchange item (EI) purchase request 908 from the buyer user device 1 for a unique EI for purchase, where the buyer user devices 1-2 receive common inventory information 808 that includes the unique EI. The EI purchase request 908 includes one or more of an EI type indicator, a brand, a price, a balance, a serial number, and a price range. For example, the processing module 902 receives an inventory query 904 from the buyer user device 1 and the processing module 902 receives an inventory query 906 from the buyer's computing device 2 within a time frame (e.g., within one second) of receiving the inventory query 904, the processing module issues inventory information 808 to the buyer's computing devices 1-2 (e.g., as retrieved from the virtual marketplace of exchange items 22), and the processing module 902 receives the EI purchase request 908 from the buyer's computing device 1 for the unique EI.

Each of the inventory queries 904 and 906 includes EI search guidance including one or more of a desired brand, one or more alternate brands, an adjacent brand indicator, a desired price, a desired price range, a desired value, a desired value range, a desired time frame for purchase, a desired discount level, and a desired discount level range. For example, each of the inventory queries 904 and 906 indicate a desired exchange item of brand y with a price range of $50-$100. The processing module 902 may organize the inventory information 808 retrieved from the database 20 by EI factors including one or more of brand, value, discount level, etc., based on the inventory queries 904 and 906. For example, the processing module 902 organizes the inventory information 808 to indicate other values and discount levels for the desired brand of the inventory queries 904 and 906 (e.g., a first EI with a brandy, value $50 with a discount level of 7%; a second EI with the brand y, value $100 with a discount level of 9%; one or more third EI with the brand y, value $200 with a discount level of 11%).

The processing module 902 may further organize the inventory information 808 by further EI factors based on other aspects of the inventory queries 904 and 906. For example, the processing module 902 organizes the inventory information 808 to further indicate values and discount levels for adjacent brands (e.g., similar category as a desired brand) to the desired brand of the inventory queries 904 and 906 (e.g., a fourth EI with a brand x, value $50 with a discount level of 8%; a fifth EI with the brand x, value $100 with a discount level of 10%; a sixth EI with the brand x, value $200 with a discount level of 12%; one or more seventh EI with a brand z, value $50 with a discount level of 6%; an eighth EI with the brand z, value $100 with a discount level of 8%; a ninth EI with the brand z, value $200 with a discount level of 10%).

Having organized the inventory information 808, the processing module 902 sends the organized inventory information 808 to each of the buyer's computing devices 1-2, where the inventory information 808 may be presented, utilizing either or both of the web browser 196 and the mobile application 198, for selection of an EI for purchase. For example, the processing module 902 receives the EI purchase request 908 from the buyer user device 1, where the EI purchase request 908 indicates that the second EI of the brand y with the value of $100 and the discount of 9% is the selected unique EI for purchase.

Having received the EI purchase request 908, the processing module 902 processes the EI purchase request 908 from the buyer's computing device 1 to complete a purchase transaction.

For example, the processing module 902 verifies user account information 868 for the buyer's computing device 1 of the user accounts 864, issue's wallet information 912 to the buyer's computing device 1 to indicate purchase of the unique EI, updates the transaction history 804 with transaction history 810 of the transaction (e.g., brand, purchase price, value, discount level, buyer identity, seller identity, etc.), and stores updated inventory information 910 in the virtual marketplace of exchange items 22 (e.g., removes the EI exchange item of the brandy, $100 value, and 9% discount level). The wallet information 912 includes a digital representation of the unique EI including one or more of EI type, brand, an image of the EI, the purchase price, the balance, serial number, the pin, and EI use rules.

FIG. 19B illustrates further steps of the example of operation of the selecting of the exchange item for purchase where the processing module 902 receives an EI purchase request 914 for the same particular exchange item that was just purchased by the buyer user device 1. When the EI of the EI purchase request 914 is unavailable, the processing module 902 issues updated inventory information 910 to the buyer's computing device 2. For example, the processing module 902 compares the desired EI of the EI purchase request 914 to inventory information 808 retrieved from the virtual marketplace of exchange items 22, indicates that the desired EI of the EI purchase request 914 is unavailable based on the comparison, generates the updated inventory information 910 based on the inventory information 808, and sends the updated inventory information 910 to the buyer user device 2.

The processing module 902 generates the updated inventory information 910 based on interpreting one or more of recent transaction history 810 and user account information 868 associated with the buyer's computing device 2 retrieved from the user accounts 864 to produce a purchasing pattern (e.g., brand preference, value level preference, discount level preference, etc.) for the buyer's computing device 2 and generating the updated inventory information 910 based on the purchasing pattern and available exchange items, e.g., list similar brand items, similar balance levels for adjacent brands, and similar discount levels for adjacent brands. The processing module 902 may further organize the updated inventory information 910 in an order based on the purchasing pattern. For example, the processing module 902 lists same brand EI's with similar balances, same brand EI's with similar discounts, adjacent brand EI's with same balances, and adjacent brand EI's with similar discount levels. Having sent the updated inventory information 910, the processing module 902 receives an updated EI purchase request 916 from the buyer's computing device 2 for another EI. Having received the updated EI purchase request 916, the processing module 902 processes the updated EI purchase request 916 to complete another transaction. For example, the processing module 902 verifies that user account information 868 for the buyer's computing device 2 is favorable, issues wallet information 918 to the buyer's computing device 2 to indicate purchase of the other EI, sends updated transaction history 810 to the database 20 to update the transaction history 804 with details of the other transaction, and rights updated inventory information 910 to the virtual marketplace of exchange items 22 within the database 20 to remove the other EI.

FIG. 19C is a flowchart illustrating an example of selecting an exchange item for purchase within an exchange item marketplace network that is performed by a server and/or a computing device. The method includes step 930 where a processing module of the server and/or the computing device receives an exchange item (EI) purchase request for a unique EI from a first buyer's computing device of a plurality of buyer's computing devices, where the first buyer's computing (or user) device selects the unique EI based on common inventory information that lists favorable availability of the unique EI. For example, the processing module receives inventory queries from the plurality of buyer user devices, issues the common inventory information to the plurality of buyer user devices, and receives a first purchase request from the first buyer user device as the EI purchase request.

The method continues at step 932 where the processing module processes the EI purchase request to produce a completed transaction. For example, the processing module verifies that user account information for the first buyer user device is favorable, issues wallet information to the first buyer user device to indicate purchase of the unique EI, updates transaction history to record information of the transaction, writes updated inventory information to a virtual marketplace of exchange items in a database (e.g., removes the unique EI and/or changes a status to unavailable).

The method continues at step 934 where the processing module receives another EI purchase request for the unique EI from a second buyer computing (or user) device, where the second buyer user device selects the unique EI based on the common inventory information. When the unique EI is unavailable for purchase, the method continues at step 936 where the processing module issues updated inventory information to the second buyer user device. The issuing includes interpreting one or more of transaction history and user account information associated with the second buyer user device to produce a purchasing pattern, generating the updated inventory information based on the purchasing pattern and available exchange items, and sending the updated inventory information to the second buyer user device.

The method continues at step 938 where the processing module receives an updated EI purchase request from the second buyer user device for another EI, where the second user device selects the other EI based on the updated inventory information. The method continues at step 940 where the processing module processes the updated EI purchase request to produce another completed transaction. For example, the processing module verifies that user account information for the second buyer user device is favorable, issues wallet information to the second buyer user device to indicate purchase of the other EI, updates transaction history to record information of the other transaction, and rights updated inventory information to the virtual marketplace of exchange items in the database (e.g., to remove the other EI).

FIG. 20A is a schematic block diagram of another embodiment of an exchange item marketplace network that includes the buyer's computing (or user) device 16 and the marketplace (MP) server(s) 18. The MP server(s) 18 includes a fraud detection 952 functional block and is coupled to the database 20.

In an example of operation of the verifying of the buyer, the server 18, via the fraud detection 952 functional block, receives an exchange item (EI) purchase request 908 from the buyer's computing device 16 to request purchase of a selected exchange item. For example, the fraud detection 952 functional block receives the EI purchase request 908 from a new buyer, where a corresponding entry within the user accounts 864 has not been established. As another example, the fraud detection 952 functional block receives the EI purchase request 908 from an existing buyer, where the corresponding entry within the user accounts 864 has been previously established.

Having received the EI purchase request 908, the fraud detection 952 functional block obtains buyer information 954 associated with the EI purchase request 908. The buyer information 954 includes one or more of a buyer user identifier (ID), user payment information (e.g., credit card information, bank account information, PayPal information, Apple Pay information, etc.), user street address, user personal information number (PIN), account activity history, history of the web browser 196, activity logs from the mobile application 198, email history, and social media information (e.g., friends, groups, topics, etc.). The obtaining of the buyer information 954 includes at least one of receiving the buyer information 954 from the buyer's computing device 16 and interpreting user account information 868 (e.g., account activity history, user payment history, etc.) extracted from the user accounts 864 retrieved from the database 20.

Having obtained the buyer information 954, the fraud detection 952 functional block obtains inventory information 808 associated with the EI purchase request 908. The obtaining includes identifying inventory traits based on the EI purchase request 908 (e.g., requested brand, requested balance), identifying inventory information 808 associated with the identified inventory traits, and retrieving the identified inventory information 808 from the virtual marketplace of exchange items 22.

Having obtained the inventory information 808, the fraud detection 952 functional block selects a fraud determination approach based on one or more of a predetermination, a system security level, the EI purchase request 908, the buyer information 954, and the inventory information 808. For example, the fraud detection 952 functional block selects the approach of a plurality of approaches based on a type of the EI purchase request 908. As another example, the fraud detection 952 functional block selects the approach based on identity of the buyer. The fraud detection approach includes utilizing a fraud decision tree in conjunction with a plurality of answers to questions, utilizing a scoring threshold for a sum of a plurality of sub-scores associated with attributes of purchasing the selected exchange item, utilizing a majority vote on a plurality of pass/fail tests, utilizing a 100% favorable results requirement for the plurality of pass/fail tests, and any combination of two or more of the fraud detection approaches.

Having selected the fraud determination approach, the fraud detection 952 functional block determines a predicted fraud level utilizing the selected fraud determination approach. For example, the fraud detection 952 functional block facilitates performing of the decision tree analysis to produce the predicted fraud level. The performing of the decision tree analysis is discussed in greater detail with reference to FIG. 20B-C.

Having determined the predicted fraud level, the fraud detection 952 functional block issues buyer verification status 956 to the buyer's computing device 16, where the buyer verification status 956 includes one of an approved buyer status, a disapproved buyer status, and a conditional approval status (e.g., contingent upon other conditions). The buyer verification status 956 may further include wallet information indicating completion of a purchasing transaction of the selected exchange item for purchase. For example, the fraud detection 952 generates the buyer verification status 956 to indicate the approved status when the predicted fraud level compares favorably to an approval threshold level. As another example, the fraud detection 952 functional block generates the buyer verification status 956 to indicate the disapproved buyer status when the predicted fraud level compares unfavorably to the approval threshold level. As yet another example, the fraud detection 952 functional block generates the buyer verification status 956 to indicate the disapproved buyer status when the predicted fraud level compares favorably to a disapproval threshold level. Having generated the buyer verification status 956, the fraud detection 952 functional block sends the buyer verification status 956 to the buyer's computing device 16, where the buyer's computing device 16 may interpret and/or display the buyer verification status 956 utilizing one or more of the web browser 196 and the mobile application 198.

FIG. 20B is a schematic block diagram of an embodiment of the fraud detection 952 functional block of FIG. 20A that is implemented via a processing module 960, which further implements a decision tree module 962 as part of the fraud detection.

In another example of operation of the verifying of the buyer, the processing module 960, having selected the fraud determination approach based on one or more of the EI purchase request 908, the user account information 868, the inventory information 808, and the buyer information 954, issues a scoring request 964 to the decision tree module 962. The scoring request 964 includes one or more of a decision tree template, a plurality of decision tree questions, a plurality of decision tree question threshold levels, a plurality of answers to at least some of the plurality of questions, a decision tree scoring approach, one or more decision tree question formulation inputs, the EI purchase request 908, the user account information 868, the inventory information 808, and the buyer information 954.

Having received the scoring request 964, the decision tree module 962 determines a decision tree from one or more decision trees and based on the scoring request 964. The determining may be based on one or more of a predetermination, interpreting the scoring request 964, system registry information, a system fraud level, an external threat assessment input, a comparison of previous estimated fraud levels and actual outcomes (e.g., interpreting transaction history), and a desired risk level. For example, the decision tree module 962 selects a decision tree, modifies a structure of the decision tree to achieve a desired level of error (e.g., rate of false positives, rate of false negatives), and updates one or more of questions and answers thresholds for elements of the modified decision tree structure to achieve the desired level of error. Having determined the decision tree, the decision tree module 962 performs a decision tree algorithm on content of the scoring request 964 utilizing the determined decision tree to produce a scoring result 966, where the decision tree algorithm traverses the determined decision tree from node to node based on the modified decision tree structure and answers to questions associated with each node that is associated with a corresponding question. For example, the decision tree module 962, for each node associated with a question of a plurality of questions of the determined decision tree, determines a corresponding answer (e.g., a hard yes, a hard no, a variable metric for comparison to a threshold), traverses to a next node of the determined decision tree based on the answer (e.g., two or more branches when branches exist within the tree structure), and determines a predicted fraud level when traversing to a node not associated with a question (e.g., a leaf node).

The determining of the predicted fraud level includes one of interpreting a hard result (e.g., fraud, okay not fraud) associated with the leaf node and generating a composite fraud score for a comparison to a fraud threshold level, where the composite fraud score is based on one or more results of nodes of the traversing of the decision tree. For example, the decision tree module 962 sums each numerical metric associated with each traversed node to produce the composite fraud score as the scoring result 966.

The processing module 960 interprets the scoring result 966 to generate the buyer verification status 956. When the hard result is utilized, the processing module 960 indicates the approved buyer status when the “okay not fraud” scoring result 966 is received. When the composite fraud score is utilized, the processing module 960 indicates the approved buyer status when the scoring result 966 compares favorably to the approved threshold level. Alternatively, when the composite fraud score is utilized, the processing module 960 indicates the disapproved buyer status when the scoring result 966 compares favorably to the disapproved threshold level.

FIG. 20C is a schematic block diagram of an embodiment of a fraud decision tree 970 that includes a plurality of nodes organized in a decision tree structure that includes branches between various nodes of the plurality of nodes in accordance with the decision tree structure. A corresponding decision tree algorithm utilizes the fraud decision tree 970 to traverse through the nodes utilizing the decision tree structure to arrive at and end node of a plurality of end nodes (e.g., leaf nodes). Each end node is associated with a scoring result, where the association includes at least one of a hard result (e.g., fraud, okay not fraud) and a variable scoring result (e.g., a varying number for comparison to a threshold determined a fraud level). Each non-end node is associated with a question of a plurality of potential questions of the fraud decision tree 970 and at least two branches based on an answer to the question, where each branch is associated with at least one of a hard yes/no answer and a calculated metric. Examples of questions associated with the fraud decision tree 970 includes is an Internet protocol address unique to a buyer user device, does a buyer email address age compare favorably to an age threshold, is a buyer credit card bank included in an approved list of banks, does a transaction amount compare favorably to a transaction threshold level, etc.

In an example of utilization of the fraud decision tree 970, a question 1 (Q1) is answered to produce a hard yes/no answer. The decision tree structure's traversed based on the answer, where a next question is Q2 when the answer is yes and the next question is Q3 when the answer is no. As another example, when utilizing variable metric answers rather than the hard yes/no answers, the answer to Q1 includes a first variable metric for comparison to a first threshold level.

When the first variable metric compares favorably to the first threshold level, the branch is taken to the next question Q2, otherwise the branch is taken to the next question Q3. As yet another example, the branching based on the hard yes/no answers or the variable metrics are utilized to determine next questions and a variable metric is produced for one or more of the answers for utilization when an end node is reached to produce a composite scoring result based on a corresponding one or more variable metrics.

The decision tree structure (e.g., which questions, branching between nodes, threshold levels) of the fraud decision tree 970 may be changed from time to time based on comparing actual fraud results to predicted fraud results. For example, the decision tree structure is optimized to reduce error and detecting fraud when approving a transaction that turns out to be fraudulent.

FIG. 20D is a flowchart illustrating an example of verifying a buyer within an exchange item marketplace network that is performed by a server and/or a computing device. The method includes step 980 where a processing module of the server and/or of the computing device receives an exchange item (EI) purchase request from a buyer user device. The receiving includes receiving the EI purchase request from a new buyer and receiving the EI purchase request from an existing buyer.

The method continues at step 982 where the processing module obtains buyer information for the buyer user device. The obtaining includes at least one of receiving the buyer information from the buyer user device and interpreting user account information from a database associated with the buyer user device. The method continues at step 984 where the processing module obtains inventory information associated with the EI purchase request.

The method continues at step 986 where the processing module selects a fraud determination approach. The selecting may be based on one or more of a predetermination, a system security level, the EI purchase request, the buyer information, and the inventory information. For example, the processing module selects an approach based on a type of EI purchase. As another example, the processing module selects the approach based on identity of the buyer (e.g., associated with a corresponding risk level).

¶ The method continues at step 988 where the processing module determines a predicted fraud level utilizing the selected fraud determination approach. For example, the processing module performs a decision tree analysis to produce the predicted fraud level when utilizing a decision tree approach. As another example, the processing module generates a plurality of sub-scores and processes the plurality of sub-scores to produce the predicted fraud level when utilizing a scoring threshold approach.¶

The method continues at step 990 where the processing module indicates a buyer verification status based on the predicted fraud level. For example, the processing module issues an approved status to the buyer user device when the predicted fraud level compares favorably to an approved threshold level. As another example, the processing module issues a disapproved status to the buyer user device when the predicted fraud level compares unfavorably to the approved threshold level. As yet another example, the processing module issues a conditional approval to the buyer user device when the predicted fraud level compares favorably to a conditional threshold level. The issuing of the conditional approval may further include generating conditions (e.g., utilizing a different form of payment as compared to a previous form of payment) associated with the conditional approval.

FIG. 21A is a schematic block diagram of another embodiment of an exchange item marketplace network that includes the buyer's computing (or user) device 16, the seller's computing (or user) device 12, a buyer's payment facility 1002, a seller's payment facility 1004, another payee's payment facility 1006, and the marketplace (MP) server(s) 18. The buyer's payment facility 1002, the seller's payment facility 1004, and the other payee's payment facility 1006 may be implemented utilizing one or more of a server, a service provider associated with one or more of a bank, a plurality of banks, and intermediate bank, a settlement bank, etc.

The MP server(s) 18 has its processing module configure to implement a purchase processing 1008 and a payment processing 1010. The database 20 stores the virtual marketplace of exchange items, the user accounts 864, the transaction history 804, and payout methods 1012.

In an example of operation of the processing of the payment, the payment processing 1010 receives purchase information 1014 from the purchase processing 1008 with regards to the exchange item purchase transaction, where the purchase processing 1008 processes the purchase of the exchange item for purchase and generates the purchase information 1014. The purchase information 1014 includes one or more of an exchange item descriptor of the transaction, a selling price, a transaction identifier (ID), a seller ID, a buyer ID, and another payee ID.

The processing of the purchase includes the purchase processing 1008 receiving an exchange item (EI) purchase request 908 from the buyer's computing device 16. The processing further includes verifying inventory availability by retrieving inventory information 808 from the virtual marketplace of exchange items 22 and verifying a buyer of the buyer's computing device 16 by accessing transaction history 810 and user account information 868 associated with the buyer. The processing further includes updating available inventory information by issuing updated inventory information 910 to the virtual marketplace of exchange items 22 and updating a digital wallet associated with the buyer's computing device 16 by issuing buyer wallet information 1028 to the buyer's computing device 16. The processing further includes informing the seller's computing device 12 of the sale by issuing sale information 1030 to the seller's computing device 12 and updating a digital wallet associated with the seller's computing device 12 by issuing seller wallet information 1032 to the seller's computing device 12 when processing of the transaction impacts the digital wallet associated with the seller's user device (e.g., when the seller is to receive payment in the form of one or more of a marketplace credit, another exchange item).

The buyer wallet information 1028 and the seller wallet information 1032 include one or more of a digital representation of an exchange item, an exchange item type, a brand, an image of an exchange item, a price, a balance, a serial number, a personal identification number (VIN), and exchange item utilization rules. The sale information 1030 includes one or more of the exchange item type, the brand, the price, the balance, serial number, the transaction ID, a timestamp, and a date.

Having received the purchase information 1014, the payment processing 1010 issues a payment request 1018 to the buyer's payment facility 1002 in accordance with buyer account information 1016 and a payout method 1022 associated with one or more of the transaction and the buyer's computing device. The payment request 1018 includes one or more of a payment vendor ID, the exchange item descriptor, the price, and the transaction ID. For example, the payment processing 1010 issues a credit card payment request to the buyer's payment facility 1002 when the payout method 1022 retrieved from the payout methods 1012 within the database 20 indicates that a credit card is to be utilized for payment, where the payment request 1018 includes account information of the buyer account information 1016 retrieved from the user accounts 864 within the database 20.

Having issued the payment request 1018, the payment processing 1010 receives payment confirmation 1020 from the buyer's payment facility 1002 (e.g., confirmation of an approved credit card transaction). The payment confirmation 1020 includes one or more of the payment vendor ID, the exchange item descriptor, the price, the transaction ID, a confirmation number, and chargeback information.

Having received the payment confirmation 1020 the payment processing 1010 determines whether the payment confirmation 1020 indicates favorable payment (e.g., approved for a later payment, payment confirmed). When the payment confirmation 1020 indicates favorable payment, the payment processing 1010 identifies a payment method for each of the seller and one or more other payee's (e.g., an exchange item marketplace network operator, financial institutions, another seller, an exchange item investor, a brand owner, a retailer, a distributor, a bulk seller, a marketplace manager). The payment method includes one or more of a payment by wire, facilitating issuing of a physical check, an automatic clearing house (ACH) payment, generating a store credit, generating a marketplace credit, transferring another exchange item, issuing a PayPal™ payment, issuing an Apple Pay™ payment, etc.

The identifying of the payment method is based on one or more of a seller payment method of the payout method 1022, seller account information 1024, other payee payment method of the payout method 1022, and other payee account information 1026. For example, the payment processing 1010 accesses the user accounts 864 to retrieve the seller account information 1024 and the other payee account information 1026 and accesses the payout methods 1012 to extract the payment methods for the seller and the other payees.

Having identified the payment methods, the payment processing 1010 issues payment distribution information 1034 to the seller's payment facility 1004 in accordance with the seller payment method and the seller account information 1024 and issues other payment distribution information 1036 to the other payee's payment facility 1006 in accordance with the other payee's payment method and the other payee account information 1026. The payment distribution information 1034 and the other payment distribution information 1036 includes one or more of the buyer ID, the payment vendor ID, the exchange item descriptor, a payment amount, the transaction ID, payee account number, a payment authorization number, and an adjustment amount (e.g., service fees, transaction fees, etc.).

FIG. 21B is a flowchart illustrating an example of processing payment within an exchange item marketplace network that is performed by a server and/or a computing device. The method includes step 1050 where a processing module of the server and/or of the computing device receives purchase information for an exchange item purchase transaction. The method continues at step 1052 where the processing module issues a payment request to a buyer payment facility. The issuing includes obtaining buyer account information and extracting a payment method associated with one or more of the buyer account information and the purchase transaction. For example, the processing module identifies a credit card account number from the buyer account information and issues a payment request to a credit card company as the buyer payment facility, where the payment request includes the credit card account number.

The method continues at step 1054 where the processing module receives payment confirmation from the buyer payment facility. For example, the processing module interprets a status (e.g., favorable payment confirmation, unfavorable payment confirmation) associated with the payment confirmation and account information for acceptance of the payment (e.g., a holding account of a market place operator).

When the payment confirmation is favorable, the method continues at step 1056 where the processing module identifies a payment method for each of a seller of the exchange item and one or more other payees. The identifying includes one or more of accessing payment method information, accessing seller account information, and accessing other payee account information. For example, the processing module identifies an automatic clearing house (ACH) method and account number for the seller and identifies a holding account for a network operator as the other payee.

The method continues at step 1058 where the processing module issues payment distribution information to a seller payment facility in accordance with a seller payment method. For example, the processing module generates the payment distribution information based on the payment method for the seller and facilitates the payment in accordance with the payment method. For instance, the processing module facilitates generating the payment distribution information to include an account number of the network operator holding account and a payment amount, and sending of the payment distribution information to a seller bank account as the seller payment facility. As another example, the processing module sends the payment distribution information to the seller payment facility in accordance with a payment time requirement of the seller payment method (e.g., sending with a one-hour time delay).

The method continues at step 1060 where the processing module issues other payment distribution information to one or more other payee payment facilities in accordance with corresponding other payee payment methods. For example, the processing module generates the other payment distribution information based on the other payee payment method and facilitates the payment in accordance with the payment method (e.g., sending immediately, sending the time delay, wiring payment, initiating an ACH, etc.).

It is noted that terminologies as may be used herein such as bit stream, stream, signal sequence, etc. (or their equivalents) have been used interchangeably to describe digital information whose content corresponds to any of a number of desired types (e.g., data, video, speech, audio, etc., any of which may generally be referred to as ‘data’).

As may be used herein, the terms “substantially” and “approximately” provides an industry-accepted tolerance for its corresponding term and/or relativity between items. Such an industry-accepted tolerance ranges from less than one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Such relativity between items ranges from a difference of a few percent to magnitude differences. As may also be used herein, the term(s) “configured to”, “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via an intervening item (e.g., an item includes, but is not limited to, a component, an element, a circuit, and/or a module) where, for an example of indirect coupling, the intervening item does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As may further be used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as “coupled to”. As may even further be used herein, the term “configured to”, “operable to”, “coupled to”, or “operably coupled to” indicates that an item includes one or more of power connections, input(s), output(s), etc., to perform, when activated, one or more its corresponding functions and may further include inferred coupling to one or more other items. As may still further be used herein, the term “associated with”, includes direct and/or indirect coupling of separate items and/or one item being embedded within another item.

As may be used herein, the term “compares favorably”, indicates that a comparison between two or more items, signals, etc., provides a desired relationship. For example, when the desired relationship is that signal 1 has a greater magnitude than signal 2, a favorable comparison may be achieved when the magnitude of signal 1 is greater than that of signal 2 or when the magnitude of signal 2 is less than that of signal 1. As may be used herein, the term “compares unfavorably”, indicates that a comparison between two or more items, signals, etc., fails to provide the desired relationship.

As may also be used herein, the terms “processing module”, “processing circuit”, “processor”, and/or “processing unit” may be a single processing device or a plurality of processing devices. Such a processing device may be a microprocessor, micro-controller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on hard coding of the circuitry and/or operational instructions. The processing module, module, processing circuit, and/or processing unit may be, or further include, memory and/or an integrated memory element, which may be a single memory device, a plurality of memory devices, and/or embedded circuitry of another processing module, module, processing circuit, and/or processing unit. Such a memory device may be a read-only memory, random access memory, volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module, module, processing circuit, and/or processing unit includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or may be distributedly located (e.g., cloud computing via indirect coupling via a local area network and/or a wide area network). Further note that if the processing module, module, processing circuit, and/or processing unit implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory element storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. Still further note that, the memory element may store, and the processing module, module, processing circuit, and/or processing unit executes, hard coded and/or operational instructions corresponding to at least some of the steps and/or functions illustrated in one or more of the Figures. Such a memory device or memory element can be included in an article of manufacture.

One or more embodiments have been described above with the aid of method steps illustrating the performance of specified functions and relationships thereof. The boundaries and sequence of these functional building blocks and method steps have been arbitrarily defined herein for convenience of description. Alternate boundaries and sequences can be defined so long as the specified functions and relationships are appropriately performed. Any such alternate boundaries or sequences are thus within the scope and spirit of the claims. Further, the boundaries of these functional building blocks have been arbitrarily defined for convenience of description. Alternate boundaries could be defined as long as the certain significant functions are appropriately performed. Similarly, flow diagram blocks may also have been arbitrarily defined herein to illustrate certain significant functionality.

To the extent used, the flow diagram block boundaries and sequence could have been defined otherwise and still perform the certain significant functionality. Such alternate definitions of both functional building blocks and flow diagram blocks and sequences are thus within the scope and spirit of the claims. One of average skill in the art will also recognize that the functional building blocks, and other illustrative blocks, modules and components herein, can be implemented as illustrated or by discrete components, application specific integrated circuits, processors executing appropriate software and the like or any combination thereof.

In addition, a flow diagram may include a “start” and/or “continue” indication. The “start” and “continue” indications reflect that the steps presented can optionally be incorporated in or otherwise used in conjunction with other routines. In this context, “start” indicates the beginning of the first step presented and may be preceded by other activities not specifically shown. Further, the “continue” indication reflects that the steps presented may be performed multiple times and/or may be succeeded by other activities not specifically shown. Further, while a flow diagram indicates a particular ordering of steps, other orderings are likewise possible provided that the principles of causality are maintained.

The one or more embodiments are used herein to illustrate one or more aspects, one or more features, one or more concepts, and/or one or more examples. A physical embodiment of an apparatus, an article of manufacture, a machine, and/or of a process may include one or more of the aspects, features, concepts, examples, etc., described with reference to one or more of the embodiments discussed herein. Further, from figure to figure, the embodiments may incorporate the same or similarly named functions, steps, modules, etc., that may use the same or different reference numbers and, as such, the functions, steps, modules, etc., may be the same or similar functions, steps, modules, etc., or different ones.

Unless specifically stated to the contra, signals to, from, and/or between elements in a figure of any of the figures presented herein may be analog or digital, continuous time or discrete time, and single-ended or differential. For instance, if a signal path is shown as a single-ended path, it also represents a differential signal path. Similarly, if a signal path is shown as a differential path, it also represents a single-ended signal path. While one or more particular architectures are described herein, other architectures can likewise be implemented that use one or more data buses not expressly shown, direct connectivity between elements, and/or indirect coupling between other elements as recognized by one of average skill in the art.

The term “module” is used in the description of one or more of the embodiments. A module implements one or more functions via a device such as a processor or other processing device or other hardware that may include or operate in association with a memory that stores operational instructions. A module may operate independently and/or in conjunction with software and/or firmware. As also used herein, a module may contain one or more sub-modules, each of which may be one or more modules.

While particular combinations of various functions and features of the one or more embodiments have been expressly described herein, other combinations of these features and functions are likewise possible. The present disclosure is not limited by the particular examples disclosed herein and expressly incorporates these other combinations. 

What is claimed is:
 1. A method for execution by one or more servers of an exchange item marketplace network, the method comprises: receiving, from a computing device of the exchange item marketplace network, an acquisition request regarding an exchange item of a plurality of exchange items of the exchange item marketplace network; obtaining user information associated with the computing device and device information associated with the computing device; selecting a fraud determination approach of a plurality of fraud determination approaches based on the user information and the device information, wherein the selected fraud determination approach includes a traversing nodes of a fraud decision tree; performing a decision tree analysis function on the fraud decision tree to produce a predicted fraud level for the acquisition request; determining whether the predicted fraud level compares favorably to a fraud threshold; and when the predicted fraud level compares favorably to the fraud threshold, facilitating execution of the acquisition request.
 2. The method of claim 1, wherein the fraud decision tree further comprises: a plurality of nodes organized in a decision tree structure, wherein the plurality of nodes includes one or more question nodes and one or more end nodes.
 3. The method of claim 2, wherein the decision tree analysis function traverses through two or more nodes of the plurality of nodes to arrive at an end node of the one or more end nodes, wherein the end node identifies the predicted fraud level.
 4. The method of claim 2, wherein the decision tree analysis function traverses through two or more nodes of the plurality of nodes to arrive at an end node of the one or more end nodes, wherein each end node of the one or more end nodes is associated with a scoring result.
 5. The method of claim 4 further comprises: generating a composite fraud score based on summing the scoring result associated with each traversed node of the fraud decision tree; and determining the predicted fraud level based on the composite fraud score.
 6. The method of claim 2,wherein the decision tree analysis function traverses through two or more nodes of the plurality of nodes to arrive at an end node of the one or more end nodes, wherein each node of the plurality of nodes is associated with a pass indication or a fail indication.
 7. The method of claim 6 further comprises: when a majority of indications are the pass indication, determining the predicted fraud level compares favorably to the fraud threshold.
 8. The method of claim 6 further comprises: when all indications are the pass indication, determining the predicted fraud level compares favorably to the fraud threshold.
 9. The method of claim 2, wherein a question node of the one or more question nodes determines whether an IP address associated with the computing device is unique to the computing device.
 10. The method of claim 2, wherein a question node of the one or more question nodes determines whether an email address age compares favorably to an email age threshold.
 11. The method of claim 2, wherein a question node of the one or more question nodes determines whether a payment instrument associated with the acquisition request is included in an approved list of payment instruments.
 12. The method of claim 2, wherein a question node of the one or more question nodes determines whether a transaction amount associated with the acquisition request compares favorably to a transaction threshold.
 13. The method of claim 1 further comprises: removing the exchange item from a digital marketplace of the exchange item marketplace network; and adding the exchange item to a digital wallet associated with the computing device.
 14. The method of claim 1 further comprises: determining to modify a structure of the fraud decision tree based on feedback regarding the executed acquisition request.
 15. The method of claim 14, wherein the modifying the structure comprises: substitution of a question node of the nodes of the fraud decision tree.
 16. The method of claim 14, wherein the modifying the structure comprises: changing a threshold level for a node of the nodes of the fraud decision tree.
 17. The method of claim 1, wherein the selecting the fraud determination approach further comprises: determining the fraud determination approach based on a type of the exchange item.
 18. The method of claim 1, wherein the selecting the fraud determination approach further comprises: determining the fraud determination approach based on a risk level associated with a user of the computing device.
 19. The method of claim 1 further comprises: when the predicted fraud level compares unfavorably to the fraud threshold: determining whether the predicted fraud level compares favorably to a conditional threshold level; and when the predicted fraud level compares favorably to a conditional threshold level, issuing a conditional approval of the acquisition request, wherein the conditional approval includes one or more conditions to be met before the execution of the acquisition request is allowed.
 20. The method of claim 1 further comprises: when the predicted fraud level compares unfavorably to the fraud threshold, denying the acquisition request. 